netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alkis Georgopoulos <alkisg@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: netdev@vger.kernel.org
Subject: Re: Bypass flow control problems
Date: Wed, 29 Dec 2010 10:47:15 +0200	[thread overview]
Message-ID: <1293612435.1813.9.camel@alkis> (raw)
In-Reply-To: <20101227134346.GD2754@reaktio.net>

Στις 27-12-2010, ημέρα Δευ, και ώρα 15:43 +0200, ο/η Pasi Kärkkäinen
έγραψε:
> You could set up QoS rules on the server to limit the network speed per client..

That sounds promising. I'll try to limit the rate of packages that the
server sends to each client to 90 Mbps and see if that works around the
flow control problem. Any tips for a good method to do that?

Thank you.


  parent reply	other threads:[~2010-12-29  8:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 17:51 Bypass flow control problems Alkis Georgopoulos
2010-12-27 13:43 ` 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 [this message]
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=1293612435.1813.9.camel@alkis \
    --to=alkisg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pasik@iki.fi \
    /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).