@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
Thanks bjeremy32 for sharing the patch!
As mentioned by Dave, I have implemented load calculation in a plugin. I can
try to reevaluate my implementation with yours as reference. Will let you know
if I get it working
Thanks bjeremy32 for sharing the patch!
As mentioned by Dave, I have implemented load calculation in a plugin. I can
try to reevaluate my implementation with yours as reference. Will let you know
if I get it working.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
If you want to refactor it in a way to fit the code architecture better, feel
free.
From: vpp-dev@lists.fd.io On Behalf Of Dave Barach
Sent: Thursday, December 17, 2020 1:43 PM
To: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
As the sole remaining original vpp author
As the sole remaining original vpp author and the area maintainer, I have
abundant experience dealing with src/vlib/{main.c, threads.c}.
In every case to date, we’ve been able to leverage existing callback hooks, or
to add callback hooks so that folks can do what they need to do (e.g. from
To: 'Ramkumar B'
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
If it will help, I will share my patch as soon as I get authorization from my
corporate overlords.
From: Ramkumar B mailto:ramukmar1...@gmail.com> >
Sent: Wednesday, December 16, 2020 11:08 AM
To:
If it will help, I will share my patch as soon as I get authorization from my
corporate overlords.
From: Ramkumar B
Sent: Wednesday, December 16, 2020 11:08 AM
To: bjerem...@gmail.com
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
I got your idea. Thanks
AM
> *To:* bjerem...@gmail.com
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Core Load Calculation
>
>
>
> The processing of the rx queue is counted toward IDLE
>
> Please explain what kind of processing. We are not doing any such rx
> processing separately. For us,
...@gmail.com>
> Cc: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] Core Load Calculation
>
> The processing of the rx queue is counted toward IDLE
> Please explain what kind of processing. We are not doing any such rx
> processing separately. For
y.
From: Ramkumar B
Sent: Wednesday, December 16, 2020 10:27 AM
To: bjerem...@gmail.com
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
The processing of the rx queue is counted toward IDLE
Please explain what kind of processing. We are not doing any such rx processi
s idle, else busy
>
>
>
> *From:* bjerem...@gmail.com
> *Sent:* Wednesday, December 16, 2020 9:25 AM
> *To:* 'Damjan Marion'
> *Cc:* 'Nick Zavaritsky' ;
> ramukmar1...@gmail.com; vpp-dev@lists.fd.io
> *Subject:* RE: [vpp-dev] Core Load Calculation
>
>
>
> No
@gmail.com> ; vpp-dev@lists.fd.io
<mailto:vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] Core Load Calculation
On 16.12.2020., at 05:45, bjerem...@gmail.com <mailto:bjerem...@gmail.com>
wrote:
What we did was to count clock cycles (timestamps) spent processing t
t; go down to 0…
>
>
>
>
>
> *From:* Damjan Marion
> *Sent:* Wednesday, December 16, 2020 3:00 AM
> *To:* bjerem...@gmail.com
> *Cc:* Nick Zavaritsky ; ramukmar1...@gmail.com;
> vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Core Load Calculation
>
>
>
>
it will go down to 0…
From: Damjan Marion
Sent: Wednesday, December 16, 2020 3:00 AM
To: bjerem...@gmail.com
Cc: Nick Zavaritsky ; ramukmar1...@gmail.com;
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
On 16.12.2020., at 05:45, bjerem...@gmail.com <mailto:bje
gt; usage per thread.
>
> From: vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io> <mailto:vpp-dev@lists.fd.io>> On Behalf Of Nick Zavaritsky
> Sent: Tuesday, December 15, 2020 1:38 PM
> To: ramukmar1...@gmail.com <mailto:ramukmar1...@gmail.com>
> Cc: vpp-dev@lis
To: ramukmar1...@gmail.com
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Core Load Calculation
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
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
17 matches
Mail list logo
