From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Three new diffserv codepoints suggested
Date: Mon, 13 Jun 2011 08:35:32 -0600 [thread overview]
Message-ID: <BANLkTikVztP4R1giZME42Vmj0iHHaFb2EQ@mail.gmail.com> (raw)
In-Reply-To: <7A482BB8-D269-4B93-A3B0-24E0C6773055@gmail.com>
On Mon, Jun 13, 2011 at 8:10 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
> I thought: Most Important Control Engrams.
Works for me. I have the classifier up at my git repo, I hope to figure out
how to get this sort of stuff into 802.11e and 802.1d next.
>
I came up with a mildly more apt name for 'Information, Text', calling
it 'Immediate Text'. There's an even better name for it:
'Bandwidth Only For Help'
For which I doubt the acronym for will get past the first PHB, but *I*
like it...
Also, I gave up, and created a new PTP diffserv class for torrents, etc
using codepoint 9 which basically combines CS1 (bulk) with the TOS bit
of MMC (minimize monetary cost)
so, four new codepoints that adaquately classify a great deal of traffic
that has come to light since the original RFC...
> Also, Linux 3.0 appears to be getting QFQ which might be a better alternative to SFQ. I've read the paper and it seems to be both clever and sufficiently simple to work.
>
I'll read it. I only just this morning get DRR into the cerowrt build...
> The key to knowledge is not to rely on others to teach you it.
Well, right now I'm trying to move Linux forward from 1998...
>
> On 11 Jun 2011, at 16:15, Dave Taht <dave.taht@gmail.com> wrote:
>
>> I was unable to come up with a back-acronym for 'mice'. I got as
>> far as 'majorly important' before getting stuck on the 'c'.
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
prev parent reply other threads:[~2011-06-13 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 13:15 Dave Taht
2011-06-12 5:05 ` Dave Taht
2011-06-13 14:10 ` Jonathan Morton
2011-06-13 14:35 ` Dave Taht [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTikVztP4R1giZME42Vmj0iHHaFb2EQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@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