Netdev List
 help / color / mirror / Atom feed
From: "Άλκης Γεωργόπουλος" <alkisg@gmail.com>
To: netdev@vger.kernel.org
Subject: r8169 - disable flow-control?
Date: Thu, 05 Mar 2009 21:35:43 +0200	[thread overview]
Message-ID: <1236281743.10409.17.camel@alkisg> (raw)

Hello,

Is there any way to disable flow control for NICs using the r8169
driver?

It would be really valuable in the following (sadly very common)
scenario:
 * r8169 gigabit NIC on the server
 * unmanaged gigabit switch that supports flow control negotiation
 * 100Mbps clients

E.g. in LTSP labs, the server can send data at ~900Mbps with flow
control off, but with flow control on the bandwidth drops to ~90Mbps.
Detailed explanation of the problem:
http://virtualthreads.blogspot.com/2006/02/beware-ethernet-flow-control.html

If the current code doesn't support it, would it be possible to add a
module parameter for this?

Kind regards,
Alkis Georgopoulos


             reply	other threads:[~2009-03-05 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 19:35 Άλκης Γεωργόπουλος [this message]
2009-03-05 21:08 ` r8169 - disable flow-control? Ben Hutchings
2009-03-05 21:29   ` Άλκης Γεωργόπουλος

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=1236281743.10409.17.camel@alkisg \
    --to=alkisg@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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