On Thu, 2006-06-07 at 11:25 -0700, Auke Kok wrote: > jamal wrote: > > [EMAIL PROTECTED]:~/Desktop/maemo$ sudo ethtool -a eth0 > > Pause parameters for eth0: > > Autonegotiate: on > > RX: off > > TX: off > > mine says it's on :)
Dell D610: [EMAIL PROTECTED]:~$ sudo lspci | grep -i bcm 0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) Whats yours? So ok, from what you say below i take it that even with the e1000s you didnt find consistency on different machines. Can you double check at least the kernels are >= 2.6.16? I can tell you this hardware that caused me problems never had flow control working in the earlier kernels. > > Maybe it is read from the eeprom and mine has it off? > > > > Again, note that: It is consuming > 10% (13-15% range) of my bandwidth. > > Granted that is at high speeds with small packets so may not be > > reflective of 96% of the world. But that would be > 50kpps of my > > forwarding capacity being chewed unreasonably. So Auke, did you say > > "performance" was what people mostly bitched about? ;-> > > yes, but that's linked with hardware that doesn't handle flowcontrol events > properly, As i mentioned earlier: This is actually hardware that works with flow control ;-> When it doesnt work - as in the case of the one i found advertising but not respecting flow control the bandwidth being consumed was > 60% ;-> To give you perspective, on average that is > 500Mbps > if you were doing large message TCP transfers over that you'd > probably see even worse performance I bet (retransmits being dropped etc). > I havent tested that, but it does seem unlikely. > Jesse is working on performance stuff, he'll gladly look into it :) > Jesse, if you want to reproduce this talk to me and i will give you a description of how to do it. Make sure you can record flow control packets both in send and receive. > >>> As said earlier, e1000 always honors the EEPROM setting for this, which > >>> has > >>> been _on_ by default for all cards (AFAIK, that is). > > > > It has _never ever_ worked on e1000 for as long as i have used e1000. If > > it was intended to work, it must have been fixed in 2.6.16. So it is new > > behavior. > > Turns out that of the e1000 cards I can find around here that are plugged in > actually are 50-50 distributed on/off, so I was wrong about it being on by > default everywhere. > > Looking back through the code I see no changes affecting flow control setup > as > early as 2.6.12 ... There are some minor (new) HW changes but nothing that > should have boken fc. > It could be something very basic. Since you have access to a variety of hardware (and variety of kernels i take it), you can go by elimination and find it. cheers, jamal - 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
