From: Dave Taht <dave.taht@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Cc: bloat-devel@lists.bufferbloat.net
Subject: Re: QoS for system critical packets on wireless
Date: Thu, 23 Jun 2011 06:32:13 -0600 [thread overview]
Message-ID: <BANLkTimB38G5fozJbXU7mUNMtgtf2EDo3g@mail.gmail.com> (raw)
In-Reply-To: <4E032511.7020508@freedesktop.org>
On Thu, Jun 23, 2011 at 5:35 AM, Jim Gettys <jg@freedesktop.org> wrote:
> On 06/22/2011 11:00 PM, Dave Taht wrote:
>>
>> On Wed, Jun 22, 2011 at 8:48 PM, Jim Gettys<jg@freedesktop.org> wrote:
>>>
>>> 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".
>>
>> I totally agree that overloading 'mice' is the wrong thing to do. mice
>> is a very useful category defined as 'short tcp streams', and well
>> discussed that way in the existing TCP literature.
>>
>> I think I've settled on ANT, but lack a suitable backronym. Ants do
>> useful stuff, taking care of cleaning up and organizing the universe.
>> They are orderly, and hard to see,
>> and can lift enormous things despite their size.
>> Given my radio background I dislike it because it's short for antenna,
>> but 'bee is confusing, and hard to spell, bird is the name of a
>> routing daemon, and I'm plumb out of ideas lacking other analogies...
>>
>>
>
> I like Bees, myself. They pollinate everything (a good analogy to what
> DNS, DHCP, et. al. do).
Too easily confused with BE, is what I meant by 'hard to spell'. I did
come up with a backronym for BEE, tho - 'Best Effort, Extreme'.
But I think I will go with Ants, at least for now.
> - Jim
>
>>> - Jim
>>>
>>> _______________________________________________
>>> Bloat-devel mailing list
>>> Bloat-devel@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/bloat-devel
>>>
>>
>>
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
next prev parent reply other threads:[~2011-06-23 12:04 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
2011-06-23 3:00 ` Dave Taht
2011-06-23 11:35 ` Jim Gettys
2011-06-23 12:32 ` Dave Taht [this message]
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=BANLkTimB38G5fozJbXU7mUNMtgtf2EDo3g@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat-devel@lists.bufferbloat.net \
--cc=jg@freedesktop.org \
/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