From: Guillaume Nault <gnault@redhat.com>
To: Matthias May <matthias.may@westermo.com>
Cc: Russell Strong <russell@strong.id.au>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: DSCP in IPv4 routing v2
Date: Tue, 14 Dec 2021 20:24:05 +0100 [thread overview]
Message-ID: <20211214192405.GA4239@pc-1.home> (raw)
In-Reply-To: <90fbc799-a9b2-beb1-68b0-2b9a9325b29b@westermo.com>
On Tue, Dec 14, 2021 at 04:58:14PM +0100, Matthias May wrote:
>
> Nevermind, i found Guillaumes talk at LPC on this topic and what the plans are to go forward.
FYI, there's now this RFC:
https://lore.kernel.org/netdev/cover.1638814614.git.gnault@redhat.com/
Note that it doesn't yet allow the use of high order DSCP bits in IPv4
rules and routes.
next prev parent reply other threads:[~2021-12-14 19:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 8:24 [PATCH net-next] net: DSCP in IPv4 routing v2 Russell Strong
2020-11-23 22:55 ` Guillaume Nault
2020-11-24 2:41 ` Russell Strong
2020-11-24 15:22 ` Guillaume Nault
2021-12-14 15:47 ` Matthias May
2021-12-14 15:58 ` Matthias May
2021-12-14 19:24 ` Guillaume Nault [this message]
2021-12-15 12:37 ` Matthias May
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=20211214192405.GA4239@pc-1.home \
--to=gnault@redhat.com \
--cc=matthias.may@westermo.com \
--cc=netdev@vger.kernel.org \
--cc=russell@strong.id.au \
/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;
as well as URLs for NNTP newsgroup(s).