From: Alkis Georgopoulos <alkisg@gmail.com>
To: netdev@vger.kernel.org
Subject: Bypass flow control problems
Date: Wed, 22 Dec 2010 19:51:31 +0200 [thread overview]
Message-ID: <1293040291.1777.36.camel@alkis> (raw)
Hi,
I'm an IT teacher/LTSP developer. In LTSP, thin clients are netbooted
from a server and receive a lot of X and remote disk traffic from it.
Many installations have a gigabit NIC on the server, an unmanaged
gigabit switch, and 100 Mbps NICs on the clients.
With flow control on, the server is limited to sending 100 Mbps to all
the clients. So with 10 thin clients the server can concurrently send
only 10 Mbps to each one of them.
On NICs that support it, we turn flow control off and the server can
properly send 100 Mbps to each client, i.e. 1 Gbps to 10 clients.
* Is there any way to bypass that problem on NICs that do not support
turning off flow control, like e.g. realteks?
I.e. when a client sends a pause signal to the server, instead of the
server pausing, to continue sending data to another client?
Or even to limit the amound of data the server sends to each client,
so that the clients never have to send pause signals?
* I really don't understand why flow control is enabled by default on
NICs and switches. In which case does it help? As far as I
understand, all it does is ruin gigabit => 100 Mbps connections...
* As a side note, since rtl8169 is a very common chipset, is there a
way to disable flow control for that specific NIC?
This problem affects thousands of LTSP installations, we'd much
appreciate your knowledge and feedback on it.
Thank you,
Alkis Georgopoulos
next reply other threads:[~2010-12-22 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 17:51 Alkis Georgopoulos [this message]
2010-12-27 13:43 ` Bypass flow control problems Pasi Kärkkäinen
2010-12-29 5:05 ` Kirsher, Jeffrey T
2010-12-29 8:47 ` Pasi Kärkkäinen
2010-12-29 8:47 ` Alkis Georgopoulos
2010-12-29 8:49 ` Pasi Kärkkäinen
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=1293040291.1777.36.camel@alkis \
--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;
as well as URLs for NNTP newsgroup(s).