From: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, cake@lists.bufferbloat.net
Subject: Re: [Cake] [PATCH net] sch_cake: diffserv8 CS1 should be bulk
Date: Thu, 27 Jan 2022 09:00:14 +0000 [thread overview]
Message-ID: <177DD195-A9B2-4502-8DA8-7CC659EBBF3B@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <87r18w3wvq.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
> On 25 Jan 2022, at 10:58, Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> Matt Johnston <matt@codeconstruct.com.au> writes:
>
>> The CS1 priority (index 0x08) was changed from 0 to 1 when LE (index
>> 0x01) was added. This looks unintentional, it doesn't match the
>> docs and CS1 shouldn't be the same tin as AF1x
>
> Hmm, Kevin, any comments?
>
> -Toke
>
I’ll have to find my thinking head & time machine :-)
This would be a lot easier if we had ‘diffserv9’, LE could have simply
been added as the ‘if you’ve really nothing better to do’ class that it
is. And it’s why I’ve personally argued for a diffserv5: lowest;low;normal;high;highest
moving on.
I think I screwed up when LE was added to diffserv8 - Matt the CS1 change from 0 to 1 IS intentional
and IIRC I tried to bump everything else up 1 to compensate.. I may have missed some things though.
Cheers,
Kevin D-B
gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-27 9:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 6:04 Matt Johnston
2022-01-25 10:58 ` Toke Høiland-Jørgensen
2022-01-25 11:54 ` Sebastian Moeller
2022-01-27 3:14 ` Matt Johnston
2022-01-27 16:00 ` Sebastian Moeller
2022-01-28 4:31 ` Matt Johnston
2022-01-27 9:00 ` Kevin 'ldir' Darbyshire-Bryant [this message]
2022-01-27 16:02 ` Sebastian Moeller
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177DD195-A9B2-4502-8DA8-7CC659EBBF3B@darbyshire-bryant.me.uk \
--to=ldir@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=toke@redhat.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