Thanks Long,
We are good now that the guidance is to stick with the netvsc pmd. Replying
here so others might see this message on the vpp mailing list.
Peter.
From: Long Li
Sent: 11 April 2022 22:39
To: Peter Morrow ; Stephen Hemminger
Cc: vpp-dev@lists.fd.io
Hello,
Is it possible to steer packets based on ‘tag’ field of IPv6 SR extension
header? I am using VPP v18.10.
I found that there are some options to do so, but there is not much explanation
of the arguments of the commands ‘classify table’, ‘classify session’.
https://docs.fd.io/vpp/18.04/srv6
Hi,
Just want to know if the mfib-lookup node is attached to the default packet
processing node graph or do we need to explicitly enable this.
Also wanted to understand if the following things are achievable with mfib in
VPP (To understand the mfib in VPP I am following
"https://wiki.fd.io/vie
Hi,
We would like to spend 5-10min doing the CSIT-2202 vpp rls notes review,
specifically recorder failures and regressions.
Vratko and me will lead that.
If there is no time on the call agenda today, no sweat, we can do it on the
next call.
Cheers,
Maciek
-=-=-=-=-=-=-=-=-=-=-=-
Links: You re
Hi everyone,
I would like to understand how VPP proceeds to fill Vectors with packets. Does
it follow any criteria to decide which packets it will group in a same vector
in order to process them together ? Is there any kind of classification ?
I can't find this information in the documentation.
Hi everyone,
Is there any command to check how many packets per vector is VPP processing ?
Thanks in advance.
David.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#21241): https://lists.fd.io/g/vpp-dev/message/21241
Mute This Topic: https://lists
Hoi David,
*show runtime* shows vectors/sec per worker thread and packets/vector per
node and clock cycles per packet.
See https://fd.io/docs/vpp/v2101/troubleshooting/cpuusage.html for more
details
groet,
Pim
On Tue, Apr 12, 2022 at 6:29 PM wrote:
> Hi everyone,
>
> Is there any command to ch
Hello,
I am on 21.01 version and looking to understand the memory allocation around
API tracing. I’ve got both Rx and Tx API trace enabled. The heap memory is
continuously going up which, I guess, is expected. “nitems” is configured to
1024 which is the default. I do see that the trace wraps a