[dpdk-dev] [PATCH v10 0/7] Expanded statistics reporting

Thomas Monjalon thomas.monjalon at 6wind.com
Thu Feb 23 09:45:27 CET 2017


2017-02-23 07:09, Remy Horton:
> 
> On 16/02/2017 10:53, Thomas Monjalon wrote:
> > 2017-02-03 10:33, Remy Horton:
> [..]
> > I think there are three remaining questions:
> > - When the metrics computation are done? (in which thread?)
> 
> Actual calculation is not done by libmetrics itself - it only handles
> distribution. Calculation is done prior to the calculated values being
> passed to rte_metrics_update_value*(), so the thread that does the
> calculation is a decision for the application.

Of course computation is not done in libmetrics. The question was about
its integration in the application and the perfromance impact.
Should it be in the dataplane threads or in separate threads?

> > - May the few lines of computation code be done differently when tightly
> > integrated in an application logic?
> 
> Yes, since it is the application itself (or in the case of bit-rate, a
> separate library) that does the calculation.

The question was more about the cache misses with this library.

> > - Could it be hosted in a separate repository on dpdk.org?
> 
> That's part of a broader discussion on how DPDK is packaged.

And specifically for these metrics libraries, do you agree it could
be packaged separately?


More information about the dev mailing list