[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <169215122333.15326.393610409728204600.git-patchwork-notify@kernel.org>
Date: Wed, 16 Aug 2023 02:00:23 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Andrea Mayer <andrea.mayer@...roma2.it>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, dsahern@...nel.org, shuah@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-kselftest@...r.kernel.org, stefano.salsano@...roma2.it,
paolo.lungaroni@...roma2.it, ahabdels.dev@...il.com,
liuhangbin@...il.com
Subject: Re: [net-next v2 0/2] seg6: add NEXT-C-SID support for SRv6 End.X
behavior
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Sat, 12 Aug 2023 20:09:24 +0200 you wrote:
> In the Segment Routing (SR) architecture a list of instructions, called
> segments, can be added to the packet headers to influence the forwarding and
> processing of the packets in an SR enabled network.
>
> Considering the Segment Routing over IPv6 data plane (SRv6) [1], the segment
> identifiers (SIDs) are IPv6 addresses (128 bits) and the segment list (SID
> List) is carried in the Segment Routing Header (SRH). A segment may correspond
> to a "behavior" that is executed by a node when the packet is received.
> The Linux kernel currently supports a large subset of the behaviors described
> in [2] (e.g., End, End.X, End.T and so on).
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] seg6: add NEXT-C-SID support for SRv6 End.X behavior
https://git.kernel.org/netdev/net-next/c/7458575a07f1
- [net-next,v2,2/2] selftests: seg6: add selftest for NEXT-C-SID flavor in SRv6 End.X behavior
https://git.kernel.org/netdev/net-next/c/1c53717c8074
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists