From: Rick Jones <rick.jones2@hp.com>
To: Tianji Li <Tianji.Li@nuim.ie>
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, 03 Mar 2011 14:33:43 -0800 [thread overview]
Message-ID: <1299191623.2157.62.camel@tardy> (raw)
In-Reply-To: <4D6FEFD4.9010608@nuim.ie>
On Thu, 2011-03-03 at 13:45 -0600, Tianji Li wrote:
>
> On 03/03/2011 12:16 PM, 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)?
> >
>
> The unit of bandwidth is something like Mbps, that of delay can be
> second, so bandwidth X delay --> Mb, which is the unit of packet size.
> So both packets and delay should have the same effect for sizing buffers.
Yet, not all packets are not created equal - in size. So, 42, 150 byte
packets queued is not the same as 42, 1500 byte packets. However, 10,
1500 byte packets is the same as 100, 150 byte packets.
Had you said something like MB and delay should have the same effect I
would have agreed with you :)
rick jones
next prev parent reply other threads:[~2011-03-03 22:34 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
2011-03-03 19:45 ` Tianji Li
2011-03-03 22:33 ` Rick Jones [this message]
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=1299191623.2157.62.camel@tardy \
--to=rick.jones2@hp.com \
--cc=Tianji.Li@nuim.ie \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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