From: d@taht.net (Dave Täht)
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: bloat-devel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] The choke scheduler, and other driver patches
Date: Sun, 20 Feb 2011 11:41:40 -0700 [thread overview]
Message-ID: <874o7ywntn.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <20110220102439.7f77f1de@s6510> (Stephen Hemminger's message of "Sun, 20 Feb 2011 10:24:39 -0800")
Stephen Hemminger <shemminger@vyatta.com> writes:
> On Sun, 20 Feb 2011 11:02:06 -0700
> d@taht.net (Dave Täht) wrote:
>
>>
>> I've been accumulating patches into my debloat branch today.[1]
>>
>> Already in there are:
>> My ath9k patch (mildly revised)
>> An e1000e patch for ethtool on my laptop
>> ar71xx patches reducing dma tx queue size
>> Kirkwood ethernet patches
>> Nathan's original iwl patch
>> linville's eBDP2 proposal
>>
>> And I wouldn't mind accumulating more.
>>
>> In particular I'm looking for the most current version of the choke
>> scheduler in the hope to play with both it and SFB. I've already
>> patched up tc for SFB, [3], it looks like patching tc for choke would
>> also be easy...
>>
>> If there are any other bufferbloat related patches I should be aware of
>> please let me know. I seem to remember another scheduler being
>> discussed, among other things, and if anyone has more knobs they can
>> expose to userspace, let me know.
>
> CHOKe is upstream in davem net-next-2.6 tree.
I knew trying to pull stuff together from wireless-testing and other
trees was going to be painful... Will cherry pick.
Are there patches to tc for choke yet?
>
--
Dave Taht
http://nex-6.taht.net
next prev parent reply other threads:[~2011-02-20 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 18:02 Dave Täht
2011-02-20 18:24 ` Stephen Hemminger
2011-02-20 18:41 ` Dave Täht [this message]
2011-02-20 20:36 ` Stephen Hemminger
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=874o7ywntn.fsf@cruithne.co.teklibre.org \
--to=d@taht.net \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=bloat@lists.bufferbloat.net \
--cc=shemminger@vyatta.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