Hi Chetan,
Something like the following should exercise using iperf and homegrown test
apps most of the components of the host stack, i.e., vcl, session layer and the
transports, including tcp:
make test-debug VPP_EXTRA_CMAKE_ARGS=-DVPP_ENABLE_SANITIZE_ADDR=ON CC=gcc-10
TEST=vcl CACHE_OUTPUT=
Hi Florin ,
This issue is coming when we are testing with iperf traffic with our
plugins that involve VPP TCP Host stack (VPP 21.06).
What's the best way to test VPP TCP host stack with Sanitizer without
involving our out of tree plugins ?
Thanks,
Chetan
On Tue, Sep 7, 2021 at 7:47 PM Florin C
Hi Neale,
Thanks for getting back. I thought as much that cloning code (even though I
do a graph node replacement) wouldn't have been the way it would be done by
someone knowledgeable in the area.
When I looked again at the code, the area I intended to change seems to be
a node in itself. *Is this
Trying to understand more about the benchmarks, couple of questions I have are:
1. In slide 6 of 1Tb/s presentation[1] it says Intel® Xeon® 6338N 32 Cores, 2.2
GHz, 42 MB Cache, but Intel arc[2] shows a cache of 48MB. I presume this is a
typo in the presentation slide.
[1] https://fd.io/present
Hi Chetan,
Out of curiosity, is this while running some make test (like the iperf3 one) or
with actual traffic through vpp?
Regards,
Florin
> On Sep 7, 2021, at 12:17 AM, chetan bhasin wrote:
>
> Hi Ben,
>
> After applying the patch , now its crashing at below place
>
> static void
> sessi
Hello all,
I am reading the news at fd.io about 1Tb/s VPP benchmark at
https://fd.io/latest/singles/terabit_ipsec/
Saw the news item and a video and slides, but not much about the hardware specs
(CPU/RAM and NICs used) or testing methods (Details of TG and DUT etc). Was
stock VPP being used or
Hi Ben,
After applying the patch , now its crashing at below place
static void
session_flush_pending_tx_buffers (session_worker_t * wrk,
vlib_node_runtime_t * node)
{
vlib_buffer_enqueue_to_next (wrk->vm, node, wrk->pending_tx_buffers,
wrk->pending_tx_nexts,
vec_len (wrk->pending_tx_nexts));
vec_
