From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org,
Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
Subject: Re: problems with e1000 and flow control
Date: Tue, 26 Feb 2008 11:06:26 -0800 [thread overview]
Message-ID: <47C46332.7040403@intel.com> (raw)
In-Reply-To: <36D9DB17C6DE9E40B059440DB8D95F52047FCD70@orsmsx418.amr.corp.intel.com>
Brandeburg, Jesse wrote:
> Wolfgang Walter wrote:
>> 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.
>
> We agree, and our latest standalone drivers have taken this into
> account, but the kernel drivers have not been updated all the way yet to
> fix this issue.
ok, that explains what is going on :)
I'll take a look into getting these changes upstream. Perhaps Wolfgang can confirm
that the driver on e1000.sf.net is properly working for him?
Auke
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-02-26 19:06 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 [this message]
2008-02-26 18:26 ` Kok, Auke
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=47C46332.7040403@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@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).