Hi Jon,
This is where ip6_sw_interface_add_del() (and other registered callbacks) are
invoked from:
call_sw_interface_add_del_callbacks
in the branch you’re using, check the signature of the function is exactly what
is expected.
/neale
De : Jonathan Richardson
Date : mardi 26 mars 2019 à
[Edited Message Follows]
Dear VPP Folks.
I have the same problem too. Nat in multi- core mode doesn't show the correct
functionality same as single core. when nat is configured, the connections
between my two clients in two sides of dut are stopped. In fact, no packet is
passed by DUT. I chec
Dear VPP Folks.
I have the same problem too. Nat in multi- core mode doesn't show the correct
functionality same as single core. when nat is configured, connections between
my two clients in two side of dut are stopped. I checked the trace of packets.
it seems the packets after walking some nod
Looks like your are running an old vPP…
You can check phymem allocation by running CLI:
vpp# show physmem
vpp# show dpdk physmem
The master code is managing phymem by itself, in other words, allocating
buffers from huge pages hold by vPP instead of DPDK. Typically, it will use 2
huge pages unl
Hi Everyone,
I am working on measuring the performance with a xconnect of two
sub-interfaces. I did see quite a few performance related questions & answers
in the community which were very helpful to get to this point. However, I’m
still facing rx and tx queue drops (“rx misses” and “tx-error”)
Hi Neale,
Thanks, that’s very helpful. ip6_sw_interface_add_del() is never called on
my system. I’m looking at the vnet/interface.h macros to figure out why.
I’m cross compiling but I see __vnet_interface_function_init_##tag##_##f is
being called on my system (looking at vnet/interface.h). I hav
