Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Dave Täht" <d@taht.net>
Cc: Van Jacobson <van@parc.com>,
	bloat-devel@lists.bufferbloat.net,
	Eric Dumazet <eric.dumazet@gmail.com>,
	bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Please enter issues into the issue tracker - Issue system organisation needed.
Date: Fri, 25 Feb 2011 10:40:36 -0500	[thread overview]
Message-ID: <20110225154036.GB15897@tuxdriver.com> (raw)
In-Reply-To: <87sjvds2r7.fsf@cruithne.co.teklibre.org>

On Thu, Feb 24, 2011 at 11:31:40AM -0700, Dave Täht wrote:
> Eric Dumazet <eric.dumazet@gmail.com> writes:
> 
> > Le jeudi 24 février 2011 à 11:32 -0500, Jim Gettys a écrit :
> >
> >> So we need better AQM algorithms and extensive testing: as you may have 
> >> seen, SFB just went into the Linux mainline this morning.
> >> 
> >
> > Indeed ;)
> 
> I would really like a sane implementation of some basic tc scripts for
> SFB and CHOKe to be out there. 
> 
> Dan Siemon's recent set of bufferbloat-related tests
> 
> http://www.coverfire.com/archives/2011/02/21/network-latency-experiments/
> 
> appeared to invoke issues between multiple queuing disciplines when
> using SFB.
> 
> Now that SFB is kernel bound, and CHOKe as well, I've merged up
> support for CHOKe and SFB into this git repo for iproute2 and the tc
> traffic control tool.
> 
> See:
> 
> https://github.com/dtaht/iproute2bufferbloat
> 
> There is a debloat-testing Linux kernel repo up at:
> 
> http://git.infradead.org/debloat-testing.git
> 
> It builds, I haven't booted into it yet. The patch set is pretty minor,
> if you already have a Linux-2.6 tree it pays to use:
> 
> git clone --references your_existing_tree  git://git.infradead.org/debloat-testing.git
> 
> (Doesn't have SFB yet, either. John?)

There now, along with a revision of my eBDP patch.  The SFQ
patches Eric identified later in this thread were already there
from 2.6.38-rc6.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      parent reply	other threads:[~2011-02-25 15:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 14:19 Jim Gettys
2011-02-24 15:00 ` [Bloat] " Fred Baker
2011-02-24 16:32   ` Jim Gettys
2011-02-24 17:08     ` Eric Dumazet
2011-02-24 18:31       ` Dave Täht
2011-02-24 19:29         ` Eric Dumazet
2011-02-25 11:21           ` GSO (was: Please enter issues into the issue tracker - Issue system organisation needed) Jesper Dangaard Brouer
2011-02-25 11:54             ` Eric Dumazet
2011-02-25 15:48               ` Jesper Dangaard Brouer
2011-02-25 16:19                 ` Eric Dumazet
2011-02-25 16:33                 ` Eric Dumazet
2011-02-25 17:15                   ` Jesper Dangaard Brouer
2011-02-26  2:41                     ` GSO Dave Täht
2011-03-02  8:30                       ` GSO Jesper Dangaard Brouer
2011-03-04  2:23                         ` GSO Dave Täht
2011-02-24 23:15         ` debloat-testing: Kitten not eaten - was Re: [Bloat] Please enter issues into the issue tracker - Issue system organisation needed Jim Gettys
2011-02-24 23:18           ` Dave Täht
2011-02-24 23:31             ` Jim Gettys
2011-02-25 15:40         ` John W. Linville [this message]

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=20110225154036.GB15897@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=bloat@lists.bufferbloat.net \
    --cc=d@taht.net \
    --cc=eric.dumazet@gmail.com \
    --cc=van@parc.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