[PATCH net-next v2 2/2] selftests: net: add new ioam tests

2024-10-02 Thread Justin Iurman
This patch re-adds the (updated) ioam selftests with support for the tunsrc feature. Signed-off-by: Justin Iurman --- tools/testing/selftests/net/Makefile |2 + tools/testing/selftests/net/config |1 + tools/testing/selftests/net/ioam6.sh | 1683

[PATCH net-next v2 0/2] selftests: net: ioam: add tunsrc support

2024-10-02 Thread Justin Iurman
is one of the changes in this patch (see the description of the topology at the top of ioam6.sh for explanations). Another change is that all IPv6 addresses used in the topology are now based on the documentation prefix (2001:db8::/32). Also, the tests have been improved and there are now many more of them

[PATCH net-next v2 1/2] selftests: net: remove ioam tests

2024-10-02 Thread Justin Iurman
This patch entirely removes the ioam selftests to prepare for the next patch in this series, which re-adds the new ioam selftests for better readability. Signed-off-by: Justin Iurman --- tools/testing/selftests/net/Makefile | 2 - tools/testing/selftests/net/config | 1

Re: [PATCH net-next] selftests: net: ioam: add tunsrc support

2024-09-23 Thread Justin Iurman
On 9/19/24 09:57, Paolo Abeni wrote: On 9/7/24 18:42, Justin Iurman wrote: TL;DR This patch comes from a discussion we had with Jakub and Paolo. This patch updates the IOAM selftests to support the new "tunsrc" feature of IOAM. As a consequence, some changes were required. For ex

[PATCH net-next] selftests: net: ioam: add tunsrc support

2024-09-07 Thread Justin Iurman
readability. Note: this patch needs this [1] iproute2-next patch to be merged (waiting for David to do so, should be done soon). [1] https://patchwork.kernel.org/project/netdevbpf/list/?series=884653 Signed-off-by: Justin Iurman --- tools/testing/selftests/net/ioam6.sh | 1832 +

Multi-threaded packet parsing ?

2019-04-07 Thread Justin Iurman
Hi all, Currently working inside IPv6 on EH and more specifically on hop-by-hop's. I was wondering if packet processing/parsing is multi-threaded or not ? Actually, I want to store per-packet EH information on net_device struct, which would be only valid for current packet processed/parsed by t