[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z2Bgh94m31sC7SIX@shredder>
Date: Mon, 16 Dec 2024 19:16:55 +0200
From: Ido Schimmel <idosch@...dia.com>
To: netdev@...r.kernel.org
Cc: davem@...emloft.net, kuba@...nel.org, pabeni@...hat.com,
edumazet@...gle.com, dsahern@...nel.org, donald.hunter@...il.com,
horms@...nel.org, gnault@...hat.com, rostedt@...dmis.org,
mhiramat@...nel.org, mathieu.desnoyers@...icios.com,
petrm@...dia.com
Subject: Re: [PATCH net-next 0/9] net: fib_rules: Add flow label selector
support
On Mon, Dec 16, 2024 at 07:11:52PM +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
> and use this information to route packets accordingly.
>
> Redirecting traffic to a routing table based on the flow label is not
> currently possible with Linux as FIB rules cannot match on it despite
> the flow label being available in the IPv6 flow key.
>
> This patchset extends FIB rules to match on the flow label with a mask.
> Future patches will add mask attributes to L4 ports and DSCP matches.
>
> Patches #1-#5 gradually extend FIB rules to match on the flow label.
>
> Patches #6-#7 allow user space to specify a flow label in route get
> requests. This is useful for both debugging and testing.
>
> Patch #8 adjusts the fib6_table_lookup tracepoint to print the flow
> label to the trace buffer for better observability.
>
> Patch #9 extends the FIB rule selftest with flow label test cases while
> utilizing the route get functionality from patch #6.
Forgot to mention, iproute2 patches can be found here:
https://github.com/idosch/iproute2/tree/submit/flowlabel_rule_v1
Powered by blists - more mailing lists