Hi Klement,
> > I see no reason why this shouldn’t be configurable.
> > [...]
> > Would you like to submit a patch?
Here is a patch making it configurable:
https://gerrit.fd.io/r/c/vpp/+/30433
Best regards,
Elias
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
What we did was to count clock cycles (timestamps) spent processing the nodes,
call this busy, and count the clock cycles spent elsewhere, call this idle. And
then simply output (busy/(busy + idle). We did this per thread and stored the
calculations globally. We then outputted the calculations
Hi All,
I am using VPP version 20.05.1 on my setup and my application is running vppctl
commands after checking that VPP process is created , but sometimes it happens
that though vpp process is created and vpp is running, still vpp doesn't accept
any vppctl commands and is giving this error:
We’ve been using flamegraphs quite successfully to see how much leeway is there.
Ex:
https://gist.githack.com/mejedi/d5d094df63faba66d413a677fcef26e3/raw/95294d36c4b180ba6741d793bf345041b00af48e/g.svg
On 15 Dec 2020, at 19:53, Ramkumar B via lists.fd.io
wrote:
Hello All,
I'm trying to
In rough terms, you can model vector size as a function of offered load [and
graph trajectory / configured features] with three linear segments.
* Dead asleep – single-digit vector sizes
* Keeping up – vector sizes up to the no-drop offered load
* Hitting the wall – vector
Hello All,
I'm trying to calculate VPP core's load. I completely understand about the
polling cores' 100% CPU usage. My requirement is different where I need to
calculate the core's load based on how much more PPS it can handle before a
packet drop occurs in the queue.
The vec/call is a good
Hi Jim,
Thank you for letting us know and volunteering to maintain the rpm builds.
I'm certainly willing to help, but have limited experience with rpms.
Also, please let us know if/when you transition to another OS and any
other CI needs.
Thanks,
-daw-
On 12/14/2020 8:33 PM, Jim Thompson
Hi all,
Just a friendly reminder that tomorrow, 16 December, we cut the stable/2101
branch and build the RC1 artifacts.
You may notice the time within the day for the milestones is earlier this
time. I changed it, because during the multiple previous occasions I ended up
staying up way
Hi Team,
I am trying to get VPP working on an interface in an gcp vm.
I am unable to ping to another VM and see that the ip4-glean errors
are there..
DBGvpp# show hardware-interfaces
NameIdx Link Hardware
GigabitEthernet0/5/0 1 up
