On Tue, Dec 19, 2006 at 11:46:34AM -0500, Joe Talbott wrote:
quoted text
> On Tue, Dec 19, 2006 at 08:10:18PM +0800, Sepherosa Ziehau wrote:
> > On 12/19/06, Joe Talbott <josepht@cstone.net> wrote:
> > >
> > >I spent some time this weekend sprinkling if_printf's throughout
> > >re_init() and this is the line where I am having trouble:
> > >
> > >        CSR_WRITE_1(sc, RE_COMMAND, RE_CMD_TX_ENB|RE_CMD_RX_ENB);
> > >
> > >By using your re2.diff and moving this line near the end of re_init()
> > >I am able to get the interface up and functioning with out panics.  I
> > >don't have any documentation than the datasheet publicly available
> > >from Realtek's web page so I'm not sure why this works or if it will
> > >work for the other chips supported by the re(4) driver.  I have a
> > >patch here:
> > >
> > >http://leaf.dragonflybsd.org/~josepht/re.diff
> > 
> > Matt's point should be correct here, RTL8101E may access descriptor
> > rings immediately after TX/RX are enabled.  In the current re(4), the
> > descriptor rings' addresses are set after TX/RX are enabled.  I tested
> > your patch on my 8169S, though it works, TX performance is only ~1/2
> > as before, so please test this one:
> > http://leaf.dragonflybsd.org/~sephe/re5.diff
> > 
> 
> This works.  How are you testing TX performance?
> 

I'm experiencing some slight packet loss on the re0 interface.

500 packets transmitted, 492 packets received, 1% packet loss
round-trip min/avg/max/stddev = 13.094/17.556/989.262/54.944 ms

I ran a second ping test from another DragonFlyBSD machine on the same
switch.  Both pings were to the same google server.  I'm sure this
will be hard to diagnose.  Please let me know if there is anything I
can do to glean more information.

Thanks,
Joe