What is the value of the MTU for your 8168 device ?
Hi Francois,
The MTU for the adapter is set at the default of 1500.
A bit more background on how I came across this might be in order. I
noticed it when performing very simple SQL queries against a postgres
database on my server. I captured the traffic on an XP client machine
using wireshark and on the linux server with tcpdump. I noticed that
although the linux server claimed to have sent 2 reply packets, XP was
seeing only the first.
What got me thinking was the fact that the time between the first and
second response packets from postgres was 0.000005 seconds (according to
the tcpdump timestamps). Another 0.4 seconds after that a retry was
attempted and the packet managed to make it though to the windows
client. I started wondering if there might be something going on with
tightly spaced packets and that's how I ended up checking the NPQ flag.
(I also looked into increasing the default interframe gap between
packets, but that didn't seem to help).
I'm happy to help with additional information including the packet
captures if you'd like to take a look.
Also, I realised after I posted that first message that having a minimum
udelay of 25us in that delay loop was probably a bit foolish. I guess I
was just so happy to have found something that worked for me that I
needed to get it off my chest before thinking it through fully. The
udelay(25) ends up increasing the minimum inter-frame gap way beyond
what should be reasonable. I haven't had a good chance to test this
yet, but I tried dropping the udelay(25) and using ndelay(10) instead
and it appeared to load the cpu less that way.
Regards,
Dave.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
