General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "David Täht" <dave.taht@gmail.com>
To: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Dealing with P2P traffic in modern networks - measurement, identification, and control
Date: Mon, 03 Oct 2011 05:03:57 -0700	[thread overview]
Message-ID: <4E89A4AD.9030802@gmail.com> (raw)
In-Reply-To: <CAGrdgiUBH5NxeEoH8Z5f5EVZD8i4MH5KK-HwJ_U2HAnVvj=4FQ@mail.gmail.com>

On 09/28/2011 11:03 AM, Jesper Louis Andersen wrote:
> On Wed, Sep 28, 2011 at 19:40, Jesper Dangaard Brouer <hawk@comx.dk> wrote:
>
>> If anybody else on the list have links/articles relating to behavioral
>> traffic classification, I'm interested! :-)
> My eTorrent uTP branch almost but not quite implement uTP in Erlang.
> It uses a LEDBAT classifier in its base, and the idea is definitely
> alluring. I have not had time testing it yet though, so I don't know
> anything about how it fares or don't. The "almost but not quite" part
> is that I skipped over some things in uTP to make other parts work
> first. I do have the LEDBAT scheduler but miss important things like
> Nagles algorithm, etc. The thesis Dave linked is quite interesting,
> but I have not yet even skimmed it.
>
I finished reading the paper today, finally, on the train from mantes la
jolie into Paris....

Aside from admiration for the scope and breadth of the analysis
(particuarly chapter 8 forward - I'm rather dubious about most
classification teniques)...

My principal question on all that work... All the models/sims were over
ethernet and assumed fairly high bandwidth connectivity.

I would really like to take a recent model showing 'fairness' of a
network protocol such as LEDBAT, and apply it to a set of wireless
connections that exhibiting the kinds of behaviors we've been seeing
(exorbitant buffering and retries)  The results should be... interesting.

Perhaps the models used here - or the real implementation(s) - can be
fed buffer sizes in excess of 1064, and delays in excess of 2 seconds
... over fairly long paths.

  reply	other threads:[~2011-10-03 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 15:56 Dave Taht
2011-09-28 17:40 ` Jesper Dangaard Brouer
2011-09-28 18:03   ` Jesper Louis Andersen
2011-10-03 12:03     ` David Täht [this message]
2011-09-28 20:51   ` grenville armitage
2011-09-29 21:58     ` Jesper Dangaard Brouer
2011-10-01  1:02       ` grenville armitage
2012-04-17  3:23     ` grenville armitage

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=4E89A4AD.9030802@gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=jesper.louis.andersen@gmail.com \
    /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