netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <sofar@foo-projects.org>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Auke Kok <auke-jan.h.kok@intel.com>,
	David Miller <davem@davemloft.net>,
	hadi@cyberus.ca, netdev@vger.kernel.org,
	jesse.brandeburg@intel.com, Robert.Olsson@data.slu.se,
	john.ronciak@intel.com, greearb@candelatech.com,
	jgarzik@pobox.com
Subject: Re: [e1000]: flow control on by default - good idea really?
Date: Wed, 05 Jul 2006 14:13:30 -0700	[thread overview]
Message-ID: <44AC2B7A.2050702@foo-projects.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0607052241230.12611@bizon.gios.gov.pl>

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, maybe e1000 only recently started to behave that way
>>> but it's the right thing to do IMHO.
>>
>> As said earlier, e1000 always honors the EEPROM setting for this, 
>> which has been _on_ by default for all cards (AFAIK, that is).
> 
> I'm not sure:
> 
> root@r1:~# ethtool -d eth0|grep flow
>       Receive flow control:              disabled
>       Transmit flow control:             disabled
> root@r2:~# ethtool -d eth0|grep flow
>       Receive flow control:              enabled
>       Transmit flow control:             enabled


Same physical NIC or different ones? In the latter case your NICs may have 
different EEPROM settings. You can dump the EEPROM and compare, do something 
like `ethtool -e eth0 raw on length 64| hexdump` for both interfaces and send 
it to me. Only the first 64 bytes should matter.

Cheers,

Auke

  reply	other threads:[~2006-07-05 21:42 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 [this message]
2006-07-06 13:03         ` jamal
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=44AC2B7A.2050702@foo-projects.org \
    --to=sofar@foo-projects.org \
    --cc=Robert.Olsson@data.slu.se \
    --cc=auke-jan.h.kok@intel.com \
    --cc=davem@davemloft.net \
    --cc=greearb@candelatech.com \
    --cc=hadi@cyberus.ca \
    --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;
as well as URLs for NNTP newsgroup(s).