On 12/6/05, Robert Olsson <[EMAIL PROTECTED]> wrote:
> jamal writes:
>
>  > Results:
>  > --------
>  >
>  > kernel 2.6.11.7: 446Kpps
>  > kernel 2.6.14: 452kpps
>  > kernel 2.6.14 with e1000-6.2.15: 470Kpps
>  > Kernel 2.6.14 with e1000-6.2.15 but rx copybreak commented out: 460Kpps
>
>  copybreaks help you..

Thanks for running these tests, so far it mostly validates that for
the general case the copybreak and prefetch benefits things.

>  > And lastly to just play with different prefetch on/off as Robert did.
>
>  Wish we could verify with some realistic traffic load
>
>  > Robert, I did notice some odd behavior with the latest driver - it comes
>  > turned on for some reason with 802 tx and receive flow control. The
>  > switch i have in the middle obeys flow control and so i was getting some
>  > _very_ incosistent results until i turned it off. Example one of the
>  > ethernets would be starved while the other got full traffic etc.
>  > Could you verify if this was affecting your results?
>
>  I'll noticed this too and turned flow control off too yes. Useless to have,
>  it makes network debugging very hard. Much better to see packet drops at
>  the systems thats not able to keep up with load. And especially now with
>  6.2.15 when RX-stats counters finally is fixed. Thanks for fixing this.

you're welcome, i think its a better measure now.  And I agree flow
control should be off for routers, but...

>  > Also - to the intel folks, any reason this behavior was made default?

Flow control is generally a good thing unless you absolutely don't
want to tell the switch to pause.  The default is configured in the
eeprom, and the driver has parameters and ethtool config for those
(like you) who need to turn it off.  For the general case of a server
or a client NIC I believe Flow control to be good.  I won't argue that
sometimes it makes performance non-deterministic however.

Regards,
  Jesse
-
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

Reply via email to