From: "John W. Linville" <linville@tuxdriver.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: bloat-devel@lists.bufferbloat.net, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
sedat.dilek@gmail.com
Subject: Re: ANNOUNCE: debloat-testing kernel git tree
Date: Thu, 3 Mar 2011 13:19:50 -0500 [thread overview]
Message-ID: <20110303181950.GD8969@tuxdriver.com> (raw)
In-Reply-To: <1299176168.2157.14.camel@tardy>
On Thu, Mar 03, 2011 at 10:16:08AM -0800, Rick Jones wrote:
> > For wireless routers and cable home gateways especially, this research
> > shows that the total un-managed buffers in your system should be less
> > than 32.
>
> Would it be a good thing to start describing these queues not so much in
> terms of packets but in terms of delay (or bandwidth X delay)?
>
> Constants tend to live longer than they should, no matter how noble in
> birth.
Yes, it probably would -- that would be more meaningful between
different technologies and/or for technologies that might have variable
latencies due to shared media or whatnot.
Now, the question becomes what patches to propose to make that
happen... :-)
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-03-03 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 22:22 John W. Linville
2011-02-27 15:23 ` Sedat Dilek
2011-02-27 15:31 ` Dave Täht
2011-02-27 15:38 ` Sedat Dilek
2011-02-27 15:56 ` Dave Täht
2011-02-27 16:01 ` Sedat Dilek
2011-02-27 16:25 ` Dave Täht
2011-03-03 18:16 ` Rick Jones
2011-03-03 18:19 ` John W. Linville [this message]
2011-03-03 19:45 ` Tianji Li
2011-03-03 22:33 ` Rick Jones
2011-03-08 6:58 ` Pavel Machek
2011-03-08 18:48 ` Rick Jones
2011-03-13 10:27 ` Pavel Machek
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=20110303181950.GD8969@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
--cc=sedat.dilek@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