On 26/08/2022 23:06, Mattias Rönnblom wrote:
On 2022-08-25 17:28, Kevin Laatz wrote:
From: Anatoly Burakov
To avoid performance impact from having lcore telemetry support, a
global
variable is exported by EAL, and a call to timestamping function is
wrapped
into a macro, so that whenever
On 29/08/2022 14:44, Morten Brørup wrote:
From: Kevin Laatz [mailto:kevin.la...@intel.com]
Sent: Monday, 29 August 2022 15.37
On 29/08/2022 13:49, Morten Brørup wrote:
From: Kevin Laatz [mailto:kevin.la...@intel.com]
Sent: Monday, 29 August 2022 14.37
The patches currently include runtime opti
> From: Kevin Laatz [mailto:kevin.la...@intel.com]
> Sent: Monday, 29 August 2022 15.37
>
> On 29/08/2022 13:49, Morten Brørup wrote:
> > From: Kevin Laatz [mailto:kevin.la...@intel.com]
> > Sent: Monday, 29 August 2022 14.37
> >> The patches currently include runtime options to enable/disable the
On 29/08/2022 13:49, Morten Brørup wrote:
From: Kevin Laatz [mailto:kevin.la...@intel.com]
Sent: Monday, 29 August 2022 14.37
The patches currently include runtime options to enable/disable the feature via
API and via telemetry endpoints. We have run performance tests and have failed
to measur
On 26/08/2022 23:06, Mattias Rönnblom wrote:
On 2022-08-25 17:28, Kevin Laatz wrote:
From: Anatoly Burakov
Currently, there is no way to measure lcore poll busyness in a
passive way,
without any modifications to the application. This patch adds a new
EAL API
that will be able to passively t
From: Kevin Laatz [mailto:kevin.la...@intel.com]
Sent: Monday, 29 August 2022 14.37
>
> The patches currently include runtime options to enable/disable the feature
> via API and via telemetry endpoints. We have run performance tests and have
> failed to measure any performance impact with the fe
On 29/08/2022 11:53, Thomas Monjalon wrote:
29/08/2022 12:41, Bruce Richardson:
On Fri, Aug 26, 2022 at 05:46:48PM +0200, Morten Brørup wrote:
From: Kevin Laatz [mailto:kevin.la...@intel.com]
Sent: Friday, 26 August 2022 17.27
On 26/08/2022 09:29, Morten Brørup wrote:
From: Jerin Jacob [mailt
> From: Bruce Richardson [mailto:bruce.richard...@intel.com]
> Sent: Monday, 29 August 2022 12.41
>
> On Fri, Aug 26, 2022 at 05:46:48PM +0200, Morten Brørup wrote:
> >
> > Also, there's a new discussion about EAL bloat [1]. Perhaps I'm
> stretching it here, but it would be nice if your library wa
29/08/2022 12:41, Bruce Richardson:
> On Fri, Aug 26, 2022 at 05:46:48PM +0200, Morten Brørup wrote:
> > > From: Kevin Laatz [mailto:kevin.la...@intel.com]
> > > Sent: Friday, 26 August 2022 17.27
> > >
> > > On 26/08/2022 09:29, Morten Brørup wrote:
> > > >> From: Jerin Jacob [mailto:jerinjac...@
On Fri, Aug 26, 2022 at 05:46:48PM +0200, Morten Brørup wrote:
> > From: Kevin Laatz [mailto:kevin.la...@intel.com]
> > Sent: Friday, 26 August 2022 17.27
> >
> > On 26/08/2022 09:29, Morten Brørup wrote:
> > >> From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> > >> Sent: Friday, 26 August 2022 1
On Sat, Aug 27, 2022 at 12:06:19AM +0200, Mattias Rönnblom wrote:
> On 2022-08-25 17:28, Kevin Laatz wrote:
> > From: Anatoly Burakov
> >
> > This patch also adds a telemetry endpoint to report lcore poll busyness, as
> > well as telemetry endpoints to enable/disable lcore telemetry. A
> > docum
On 2022-08-25 17:28, Kevin Laatz wrote:
From: Anatoly Burakov
Currently, there is no way to measure lcore poll busyness in a passive way,
without any modifications to the application. This patch adds a new EAL API
that will be able to passively track core polling busyness.
There's no generic
> From: Kevin Laatz [mailto:kevin.la...@intel.com]
> Sent: Friday, 26 August 2022 17.27
>
> On 26/08/2022 09:29, Morten Brørup wrote:
> >> From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> >> Sent: Friday, 26 August 2022 10.16
> >>
> >> On Fri, Aug 26, 2022 at 1:37 PM Bruce Richardson
> >> wrote
On 26/08/2022 09:29, Morten Brørup wrote:
From: Jerin Jacob [mailto:jerinjac...@gmail.com]
Sent: Friday, 26 August 2022 10.16
On Fri, Aug 26, 2022 at 1:37 PM Bruce Richardson
wrote:
On Fri, Aug 26, 2022 at 12:35:16PM +0530, Jerin Jacob wrote:
On Thu, Aug 25, 2022 at 8:56 PM Kevin Laatz
wrot
> From: Jerin Jacob [mailto:jerinjac...@gmail.com]
> Sent: Friday, 26 August 2022 10.16
>
> On Fri, Aug 26, 2022 at 1:37 PM Bruce Richardson
> wrote:
> >
> > On Fri, Aug 26, 2022 at 12:35:16PM +0530, Jerin Jacob wrote:
> > > On Thu, Aug 25, 2022 at 8:56 PM Kevin Laatz
> wrote:
> > > >
> > > > Fr
On Fri, Aug 26, 2022 at 1:37 PM Bruce Richardson
wrote:
>
> On Fri, Aug 26, 2022 at 12:35:16PM +0530, Jerin Jacob wrote:
> > On Thu, Aug 25, 2022 at 8:56 PM Kevin Laatz wrote:
> > >
> > > From: Anatoly Burakov
> > >
> > > Currently, there is no way to measure lcore poll busyness in a passive
>
On Fri, Aug 26, 2022 at 12:35:16PM +0530, Jerin Jacob wrote:
> On Thu, Aug 25, 2022 at 8:56 PM Kevin Laatz wrote:
> >
> > From: Anatoly Burakov
> >
> > Currently, there is no way to measure lcore poll busyness in a passive way,
> > without any modifications to the application. This patch adds a n
On Thu, Aug 25, 2022 at 8:56 PM Kevin Laatz wrote:
>
> From: Anatoly Burakov
>
> Currently, there is no way to measure lcore poll busyness in a passive way,
> without any modifications to the application. This patch adds a new EAL API
> that will be able to passively track core polling busyness.
From: Anatoly Burakov
Currently, there is no way to measure lcore poll busyness in a passive way,
without any modifications to the application. This patch adds a new EAL API
that will be able to passively track core polling busyness.
The poll busyness is calculated by relying on the fact that mo
19 matches
Mail list logo
