Re: [dpdk-dev] [PATCH] latency: clear mbuf timestamp after latency calculation

Hi, Thanks, I have sent a v2. Any comment on the problem of dropped mbuf that I described in the cover letter? In our application the max_latency_ns metric is useless since after running for a while it would always take on obviously incorrect value (up to a few minutes). I suspect the impact o

Re: [dpdk-dev] [PATCH] latency: clear mbuf timestamp after latency calculation

Hi, > -Original Message- > From: long...@viettel.com.vn [mailto:long...@viettel.com.vn] > Sent: Wednesday, September 19, 2018 9:23 AM > To: Pattan, Reshma > Cc: dev@dpdk.org; Bao-Long Tran ; > sta...@dpdk.org > Subject: [PATCH] latency: clear mbuf timestamp after latency calculation > >

[dpdk-dev] [PATCH] latency: clear mbuf timestamp after latency calculation

The timestamp of a mbuf should be cleared after that mbuf was used for latency calculation, otherwise future packets which reuse the same mbuf would inherit that previous timestamp. The latencystats library looks for mbuf with non-zero timestamp, thus incorrectly inherited value would result in inc

[dpdk-dev] [PATCH] latency: clear mbuf timestamp after latency calculation

The timestamp of a mbuf should be cleared after that mbuf was used for latency calculation, otherwise future packets which reuse the same mbuf would inherit that previous timestamp. The latencystats library looks for mbuf with non-zero timestamp, thus incorrectly inherited value would result in inc