From: Jim Gettys <jg@freedesktop.org>
To: bloat-devel@lists.bufferbloat.net
Subject: Re: QoS for system critical packets on wireless
Date: Wed, 22 Jun 2011 22:48:29 -0400 [thread overview]
Message-ID: <4E02A97D.8010007@freedesktop.org> (raw)
In-Reply-To: <BANLkTim7M52YcJKo6w34sMO7fYpp44OayA@mail.gmail.com>
On 06/22/2011 11:17 AM, Dave Taht wrote:
> The biggest fallout of the diffserv work I was trying was observing
> that most packets fell into one of 3 buckets:
>
> 1) System control and 'MICE' are< less than 1% of all packets. Mice
> includes a bunch of messages like ARP, NTP, UDP, and most of the icmp6
> portion of the stack, in what I'm doing currently. Mice are
> desperately needed for the network to continue to function.
I'd not use this term: please call it something else.
Van and Kathy have talked about HTTP "mice" and "elephant" TCP flows for
a long time, and you'll terminally confuse everyone if you call these
items "mice".
- Jim
next prev parent reply other threads:[~2011-06-23 2:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:17 Dave Taht
2011-06-22 22:12 ` [Babel-users] " Juliusz Chroboczek
2011-06-23 15:50 ` Dave Taht
2011-06-24 12:52 ` Juliusz Chroboczek
2011-06-24 14:07 ` Dave Taht
2011-06-23 2:48 ` Jim Gettys [this message]
2011-06-23 3:00 ` Dave Taht
2011-06-23 11:35 ` Jim Gettys
2011-06-23 12:32 ` Dave Taht
2011-06-23 17:23 ` Rick Jones
2011-06-23 18:38 ` Justin McCann
2011-06-26 13:51 ` Dave Taht
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=4E02A97D.8010007@freedesktop.org \
--to=jg@freedesktop.org \
--cc=bloat-devel@lists.bufferbloat.net \
/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