From: Guillaume Nault <gnault@redhat.com>
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, horms@kernel.org,
donald.hunter@gmail.com, dsahern@kernel.org, petrm@nvidia.com
Subject: Re: [PATCH net-next 0/6] net: fib_rules: Add DSCP mask support
Date: Fri, 21 Feb 2025 16:29:31 +0100 [thread overview]
Message-ID: <Z7ib21vF8rJ5K+Pe@debian> (raw)
In-Reply-To: <20250220080525.831924-1-idosch@nvidia.com>
On Thu, Feb 20, 2025 at 10:05:19AM +0200, Ido Schimmel wrote:
> In some deployments users would like to encode path information into
> certain bits of the IPv6 flow label, the UDP source port and the DSCP
> field and use this information to route packets accordingly.
>
> Redirecting traffic to a routing table based on specific bits in the
> DSCP field is not currently possible. Only exact match is currently
> supported by FIB rules.
>
> This patchset extends FIB rules to match on the DSCP field with an
> optional mask.
>
Reviewed-by: Guillaume Nault <gnault@redhat.com>
next prev parent reply other threads:[~2025-02-21 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 8:05 [PATCH net-next 0/6] net: fib_rules: Add DSCP mask support Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 1/6] net: fib_rules: Add DSCP mask attribute Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 2/6] ipv4: fib_rules: Add DSCP mask matching Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 3/6] ipv6: " Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 4/6] net: fib_rules: Enable DSCP mask usage Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 5/6] netlink: specs: Add FIB rule DSCP mask attribute Ido Schimmel
2025-02-20 8:05 ` [PATCH net-next 6/6] selftests: fib_rule_tests: Add DSCP mask match tests Ido Schimmel
2025-02-21 15:29 ` Guillaume Nault [this message]
2025-02-22 0:30 ` [PATCH net-next 0/6] net: fib_rules: Add DSCP mask support patchwork-bot+netdevbpf
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=Z7ib21vF8rJ5K+Pe@debian \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.