Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: Jim Gettys <jg@freedesktop.org>
Cc: "linville@gmail.com" <linville@gmail.com>,
	bloat-devel@lists.bufferbloat.net
Subject: Re: debloat-testing: Kitten not eaten - was Re: [Bloat] Please enter issues into the issue tracker - Issue system organisation needed.
Date: Thu, 24 Feb 2011 16:18:49 -0700	[thread overview]
Message-ID: <87vd09ja1y.fsf@cruithne.co.teklibre.org> (raw)
In-Reply-To: <4D66E680.3060306@freedesktop.org> (Jim Gettys's message of "Thu,  24 Feb 2011 18:15:12 -0500")

Jim Gettys <jg@freedesktop.org> writes:

> On 02/24/2011 01:31 PM, Dave Täht wrote:
>
>> 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?)
>
> I built it; it booted, worked on my eDP display, and did my usual ping
> + scp test (to a local system, so that the 802.11 would be saturated).
>
> OOTB, it controls the latency quite decently (no more than a few
> milliseconds), but the drop rate on the ICMP running at the same time

This brings the iwl driver down from 130+ms to a few ms!?

How many more orders of magnitude do you need for *awesome*, rather than decent?

> is quite high (~25%).  Pretty uncontrolled experiment; my son is home
> ;-).

That IS high. Perhaps the iwl and the linvilles alg are competing
overmuch. Does your card do aggregation?

> 			- Jim
>

-- 
Dave Taht
http://nex-6.taht.net

  reply	other threads:[~2011-02-24 23:19 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 [this message]
2011-02-24 23:31             ` Jim Gettys
2011-02-25 15:40         ` John W. Linville

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=87vd09ja1y.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --cc=bloat-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.org \
    --cc=linville@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