Hi Reshma,
I mean in the latencystats document. A few lines about what is taken away
by the library (the mbuf timestamp when PKT_RX_TIMESTAMP is set) would be
very helpful.
Best regards,
BL
- Original Message -
From: "reshma pattan"
To: long...@viettel.com.vn
Cc: "Konstantin Ananyev" ,
Hi,
> -Original Message-
> From: long...@viettel.com.vn [mailto:long...@viettel.com.vn]
> Sent: Saturday, September 22, 2018 3:58 AM
> To: Pattan, Reshma ; Ananyev, Konstantin
> ; dev@dpdk.org
> Subject: RE: [PATCH] latencystats: fix timestamp marking and latency
> calculation
>
> Hi Resh
> -Original Message-
> From: reshma.pat...@intel.com [mailto:reshma.pat...@intel.com]
> Sent: Friday, September 21, 2018 11:02 PM
> To: long...@viettel.com.vn; konstantin.anan...@intel.com; dev@dpdk.org
> Cc: Reshma Pattan
> Subject: [PATCH] latencystats: fix timestamp marking and latency
Hi Reshma,
> -Original Message-
> From: reshma.pat...@intel.com [mailto:reshma.pat...@intel.com]
> Sent: Friday, September 21, 2018 11:02 PM
> To: long...@viettel.com.vn; konstantin.anan...@intel.com; dev@dpdk.org
> Cc: Reshma Pattan
> Subject: [PATCH] latencystats: fix timestamp marking
Latency calculation logic is not correct for the case where
packets gets dropped before TX. As for the dropped packets,
the timestamp is not cleared, and such packets still gets
counted for latency calculation in next runs, that will result
in inaccurate latency measurement.
So fix this issue as b
5 matches
Mail list logo
