Hello,
We are integrating VPP into our product.
One question we had was about the recommendation for usage of cores.
When using DPDK, the recommendation is to allocate it one physical core.
When using HyperThreaded cores, for DPDK one core is allocated and sibling core
is not allocated to
**When: *Tuesday April 28, 2020 1800 UTC to 2200 UTC*
*
*
*What: *Linux foundation upgrades, OS updates, and security patches
* Jenkins
o Upgrade to 2.222.x
o OS and security updates
o Plugin updates
* Nexus
o Upgrade to 2.14.17-01
o OS and security updates
*
Hi Ole!
Thanks, here is a change doing that, please have a look:
https://gerrit.fd.io/r/c/vpp/+/26544
With this change, an assertion will fail if the number of threads is
greater than 55 or something like that. To make things work for such
large thread counts it would be necessary to increase
Hi Elias,
Thank you for the thorough analysis.
I think the best approach for now is the one you propose. Reserve as many slots
as you have workers.
Potentially also increase the queue size > 64.
Damjan is looking at some further improvements in this space, but for now
please go with what you
Hi all
I've noticed that if port of collector in IPFIX configuration is set to
different value than the default is, e.g. instead of 4739 which is the
default, then packets with template will arrive at the configured port,
but packets with data will still go to port 4739.
Bug in Jira
Hi Dimitar,
In VPP’s FIB weight and preference are attributes of a path not of a route. The
weight controls [un]equal cost load-balancing across the paths and preference
controls which paths to use when they are [un]available (i.e. BFD down), a kind
of poor man’s fast re-route.
It’s my
