[PATCH v2 2/2] test/pcapng: test chained mbufs

2024-09-13 Thread Oleksandr Nahnybida
Adjust test to check if pcapng works with chained mbufs Signed-off-by: Oleksandr Nahnybida --- Sorry for the mess. Resending PATCH v2 2/2 as the previous submission was incorrectly threaded to the v1. Please ignore the earlier email app/test/test_pcapng.c | 12 ++-- 1 file changed, 10

[PATCH v2 2/2] test/pcapng: test chained mbufs

2024-09-13 Thread Oleksandr Nahnybida
Adjust test to check if pcapng works with chained mbufs Signed-off-by: Oleksandr Nahnybida --- Resending PATCH v2 2/2 as the previous submission was incorrectly threaded to the v1. Please ignore the earlier email app/test/test_pcapng.c | 12 ++-- 1 file changed, 10 insertions(+), 2

[PATCH v2 2/2] test/pcapng: test chained mbufs

2024-09-13 Thread Oleksandr Nahnybida
Adjust test to check if pcapng works with chained mbufs Signed-off-by: Oleksandr Nahnybida --- app/test/test_pcapng.c | 12 ++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/app/test/test_pcapng.c b/app/test/test_pcapng.c index 2665b08c76..b219873c3a 100644 --- a/app

[PATCH v2 1/2] pcapng: fix handling of chained mbufs

2024-09-13 Thread Oleksandr Nahnybida
chain to disk. This fix ensures that the block length is calculated based on the pkt_len, aligning it with the actual data written to disk. Signed-off-by: Oleksandr Nahnybida --- v2 - fixed typo in signoff email lib/pcapng/rte_pcapng.c | 12 ++-- 1 file changed, 6 insertions(+), 6

[PATCH 1/2] pcapng: fix handling of chained mbufs

2024-09-13 Thread Oleksandr Nahnybida
chain to disk. This fix ensures that the block length is calculated based on the pkt_len, aligning it with the actual data written to disk. Signed-off-by: Oleksandr Nahnybida --- lib/pcapng/rte_pcapng.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/lib/pcapng

rte_mempool_create/alloc_seg crash

2024-05-13 Thread Oleksandr Nahnybida
Hi All, I have a crash inside of rte_mempool_create which happens when I allocate multiple big mem pools(multiple GB each), in particular first argument of function alloc_seg(LINUX) is null, I investigated a little bit and it seems like there is a bug inside of rte_fbarray_find_next_n_free. Insid