From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jamal Hadi Salim" <jhs@mojatatu.com>,
"Cong Wang" <xiyou.wangcong@gmail.com>,
"Jiri Pirko" <jiri@resnulli.us>,
"Paolo Abeni" <pabeni@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] [PATCH net-next] sch_cake: Take into account guideline DEF/DGSIC/36 from French Administration
Date: Mon, 28 Mar 2022 16:19:30 +0000 [thread overview]
Message-ID: <079a3b29-fec7-97c9-19d9-0bd9a17e63f1@csgroup.eu> (raw)
In-Reply-To: <87bkxq5bgt.fsf@toke.dk>
Le 28/03/2022 à 17:43, Toke Høiland-Jørgensen a écrit :
> Christophe Leroy <christophe.leroy@csgroup.eu> writes:
>
>> French Administration has written a guideline that defines additional
>> DSCP values for use in its networks.
>
> Huh, that's interesting!
>
>> Add new CAKE diffserv tables to take those new values into account
>> and add CONFIG_NET_SCH_CAKE_DGSIC to select those tables instead of
>> the default ones.
>
> ...however I don't think we should be including something this
> special-purpose into the qdisc kernel code, and certainly we shouldn't
> have a config option that changes the meaning of the existing diffserv
> keywords!
By the way it doesn't really change meaning. Just enhances it indeed.
Because they are not changing the meaning of existing DSCP codes, just
adding new ones.
>
> Rather, this is something that is best specified from userspace; and in
> fact Cake already has no less than two different ways to do this: the
> 'fwmark' option, and setting the skb->priority field. Have you tried
> using those?
No I have not. In fact I'm just discovering the subject after some
people told me "we are contractually required to apply this guideline,
please make sure Linux kernel supports it".
I'll give 'fwmark' and/or skb->priority a try. Is there any
Documentation on that somewhere ?
Thanks
Christophe
next prev parent reply other threads:[~2022-03-28 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 12:03 Christophe Leroy
2022-03-28 15:43 ` Toke Høiland-Jørgensen
2022-03-28 16:19 ` Christophe Leroy [this message]
2022-03-28 16:42 ` Toke Høiland-Jørgensen
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=079a3b29-fec7-97c9-19d9-0bd9a17e63f1@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=cake@lists.bufferbloat.net \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=toke@toke.dk \
--cc=xiyou.wangcong@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