ge-
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Pattan, Reshma
> > Sent: Friday, September 21, 2018 12:15 PM
> > To: long...@viettel.com.vn
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] Incorrect latencystats implementation
> >
> >
Hi Reshma,
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Pattan, Reshma
> Sent: Friday, September 21, 2018 12:15 PM
> To: long...@viettel.com.vn
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Incorrect latencystats implementation
>
>
Hi,
> -Original Message-
> From: long...@viettel.com.vn [mailto:long...@viettel.com.vn]
> Sent: Friday, September 21, 2018 2:58 AM
> To: Pattan, Reshma
> Cc: dev@dpdk.org
> Subject: RE: Incorrect latencystats implementation
>
> Hi Reshma,
>
> > -Original Message-
> > From: reshm
Hi Reshma,
> -Original Message-
> From: reshma.pat...@intel.com [mailto:reshma.pat...@intel.com]
> Sent: Thursday, September 20, 2018 8:09 PM
> To: long...@viettel.com.vn
> Cc: dev@dpdk.org
> Subject: RE: Incorrect latencystats implementation
>
>
>
> > -Original Message-
> > Fro
> -Original Message-
> From: long...@viettel.com.vn [mailto:long...@viettel.com.vn]
> Sent: Wednesday, September 19, 2018 9:17 AM
> To: Pattan, Reshma
> Cc: dev@dpdk.org; Bao-Long Tran
> Subject: Incorrect latencystats implementation
>
>
> I have submit a patch to implement the trivi
Currently, lib latencystats works as follow:
* For every sample period, one packet is selected by RX callback to be later
used for latency measurement. That packet is marked with a timestamp.
* In TX callback, mbufs with non-zero timestamp are used for calculation.
I see a problem
6 matches
Mail list logo
