General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat@lists.bufferbloat.net, "Nathaniel J. Smith" <njs@pobox.com>
Subject: Re: [Bloat] debloat-testing tree rebased, some patches dropped
Date: Wed, 30 Mar 2011 22:19:17 +0200	[thread overview]
Message-ID: <1301516357.2679.1.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTi=LmzmwFgMV1a+KRZpUW7xE+TjCMUHYx5vXbNaV@mail.gmail.com>

Le mercredi 30 mars 2011 à 16:06 -0400, Dave Taht a écrit :

> I was under the impression there were several other packet schedulers
> in the works
> 

Yep, QFQ missed linux-2.6.39 merge window.

It is ready and should land in linux-2.6.40




  reply	other threads:[~2011-03-30 20:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 19:11 John W. Linville
2011-03-30 20:06 ` Dave Taht
2011-03-30 20:19   ` Eric Dumazet [this message]
2011-03-30 20:32   ` Jonathan Morton

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=1301516357.2679.1.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=njs@pobox.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