public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: jgarzik@pobox.com, greearb@candelatech.com,
	john.ronciak@intel.com, Robert.Olsson@data.slu.se,
	jesse.brandeburg@intel.com, netdev@vger.kernel.org,
	David Miller <davem@davemloft.net>,
	Auke Kok <auke-jan.h.kok@intel.com>
Subject: Re: [e1000]: flow control on by default - good idea really?
Date: Thu, 06 Jul 2006 09:03:38 -0400	[thread overview]
Message-ID: <1152191018.5103.48.camel@jzny2> (raw)
In-Reply-To: <Pine.LNX.4.64.0607052241230.12611@bizon.gios.gov.pl>

On Wed, 2006-05-07 at 22:45 +0200, Krzysztof Oledzki wrote:
> 
> On Wed, 5 Jul 2006, Auke Kok wrote:
> 
> > David Miller wrote:
> >> From: jamal <hadi@cyberus.ca>
> >> Date: Tue, 04 Jul 2006 15:20:39 -0400
> >> 
> >>> BTW, As an addendum this default behavior changed around 2.6.16 it
> >>> seems.
> >> 
> >> Flow control has been on by default in the tg3 driver since the
> >> beginning, 

Are you sure about this Dave?;-> because I do have a tg3 on my laptop.

hadi@jzny2:~/Desktop/maemo$ sudo ethtool -a eth0
Pause parameters for eth0:
Autonegotiate:  on
RX:             off
TX:             off

hadi@jzny2:~/Desktop/maemo$ uname -a
Linux jzny2 2.6.16 #6 Fri Jun 9 15:29:40 EDT 2006 i686 GNU/Linux
hadi@jzny2:~/Desktop/maemo$

Maybe it is read from the eeprom and mine has it off?

> maybe e1000 only recently started to behave that way
> >> but it's the right thing to do IMHO.
> >

I will continue testing when i get proper hardware and post. And if only
Robert and I are whining about this, we are adults and we can turn it
off. I never tried it with large packets, so it may be helpful there
for forwarding.

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? ;->

> > 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.

> I'm not sure:
> 
> root@r1:~# mii-tool -v eth0

Try ethtool -a eth0 to read and -A to set.

cheers,
jamal


  parent reply	other threads:[~2006-07-06 13:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 17:11 [e1000]: flow control on by default - good idea really? jamal
2006-07-04 19:20 ` jamal
2006-07-05 16:23   ` Auke Kok
2006-07-05 20:37     ` Krzysztof Oledzki
2006-07-05 18:22   ` David Miller
2006-07-05 18:32     ` Auke Kok
2006-07-05 20:45       ` Krzysztof Oledzki
2006-07-05 21:13         ` Auke Kok
2006-07-06 13:03         ` jamal [this message]
2006-07-06 18:25           ` Auke Kok
2006-07-07  3:09             ` jamal
2006-07-07  6:59           ` David Miller
2006-07-07 12:28             ` jamal
2006-07-20 20:15               ` Bug in e1000 + semantics of flow control WAS(Re: " jamal
2006-08-03 12:29                 ` jamal
2006-10-16 18:55               ` Auke Kok
2006-10-17 13:05                 ` jamal
2006-10-17 17:18                   ` Auke Kok
2006-10-17 18:25                   ` Stephen Hemminger
2006-10-17 21:02                   ` Auke Kok
2006-10-18 13:35                     ` jamal
2006-10-18 14:57                       ` Auke Kok
2006-10-17 21:46                   ` David Miller
2006-07-05 16:57 ` Robert Olsson
2006-07-05 18:21 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2006-07-07  4:43 Michael Chan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1152191018.5103.48.camel@jzny2 \
    --to=hadi@cyberus.ca \
    --cc=Robert.Olsson@data.slu.se \
    --cc=auke-jan.h.kok@intel.com \
    --cc=davem@davemloft.net \
    --cc=greearb@candelatech.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=olel@ans.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox