netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
Cc: netdev@vger.kernel.org
Subject: Re: problems with e1000 and flow control
Date: Tue, 26 Feb 2008 10:26:41 -0800	[thread overview]
Message-ID: <47C459E1.1050803@intel.com> (raw)
In-Reply-To: <200802252015.49862.wolfgang.walter@studentenwerk.mhn.de>

Wolfgang Walter wrote:
> Hello,
> 
> it seems that e1000 enables flow-control (rx pause frames) even if the switch 
> does not advertise flow control. This seems to get a problem as (at least 
> some) switches then forward pause frames directed to the card from other 
> hosts. We think there are hosts which indeed do this in the lans of our 
> student halls.
> 
> I think flow control should be completely disabled by default if the switch 
> does not advertise it. It still can be forced with ethtool.

Are you sure that the switch actually advertises the flow control "disabled"
setting properly? Perhaps you can include the e1000 ethtool flow control settings
and dmesg output (2.6.24 will print out FC status when link comes up).

There's a lengthy argumentation including spec references in the e1000/e1000e
driver code on how FC is handled (look for "IEEE 802.3ab"). Can you take a look at
that and see what might be happening?

Changing this behaviour might give other people issues which is something we need
to be very cautious about, obviously :)

Cheers,

Auke

      parent reply	other threads:[~2008-02-26 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-25 19:15 problems with e1000 and flow control Wolfgang Walter
2008-02-26 18:10 ` Brandeburg, Jesse
2008-02-26 19:06   ` Kok, Auke
2008-02-26 18:26 ` Kok, Auke [this message]

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=47C459E1.1050803@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=wolfgang.walter@studentenwerk.mhn.de \
    /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).