General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Luca Dionisi <luca.dionisi@gmail.com>
To: bufferbloat list <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] About LEDBAT, µTP and BitTorrent
Date: Fri, 4 Feb 2011 11:18:23 +0100	[thread overview]
Message-ID: <AANLkTikhXG40k7d1Ujmb+2jZkMFb_-nQJN92xs26cywJ@mail.gmail.com> (raw)
In-Reply-To: <87ei7odsjl.fsf@trurl.pps.jussieu.fr>

On Fri, Feb 4, 2011 at 11:04 AM, Juliusz Chroboczek <jch@pps.jussieu.fr> wrote:
>> I think that the 2 things have to be carried on independently,
>
> Yes.
>
>> The problem is that one cannot make sure that end users will act
>> fairly, by adjusting their sending rate.  The only way to do this is
>> dropping packets, so that they are obliged to send again.
>
> Well, the issues of increased delay and greedy, unresponsive flows are,
> to a certain extent, distinct.  One can image AQMs that are only
> concerned with penalising unresponsive flows but don't do anything to
> reduce buffer size when all flows are well-behaved.  Conversely, one can
> imagine solving the buffer bloat problem on the assumption that all
> flows are TCP-friendly.

I don't get it. Why do we need to make such an assumption?
If the routers keep a low buffer size (better if dynamically, if I am
correct) and much better if they *also* implement a AQM which
rate-limit the unresponsive flows, then we will have almost solved the
problem and *also* actually discouraged unfair behavior from clients.

  reply	other threads:[~2011-02-04 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04  9:36 Juliusz Chroboczek
2011-02-04  9:55 ` Luca Dionisi
2011-02-04 10:04 ` Juliusz Chroboczek
2011-02-04 10:18   ` Luca Dionisi [this message]
2011-02-04 10:23     ` Luca Dionisi
2011-02-04 10:39     ` Juliusz Chroboczek

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTikhXG40k7d1Ujmb+2jZkMFb_-nQJN92xs26cywJ@mail.gmail.com \
    --to=luca.dionisi@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /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