> -----Original Message-----
> From: long...@viettel.com.vn [mailto:long...@viettel.com.vn]
> Sent: Wednesday, September 19, 2018 9:17 AM
> To: Pattan, Reshma <reshma.pat...@intel.com>
> Cc: dev@dpdk.org; Bao-Long Tran <long...@viettel.com.vn>
> Subject: Incorrect latencystats implementation
>
>
> I have submit a patch to implement the trivial fix. For the drop case I can
> think of 2 options. We can either clear timestamp when putting mbufs back
> to their pool, or change lib latencystats implementation to perform packet
> selection at TX callback and let RX callback add timestamp to every packet.
> Both option could affect performance but I think the second option is less
> aggressive.
What happens when applications drop the packets? Do they free the mbuf?
In such case, can application set the timestamp to 0 before freeing the mbuf,
instead of making
these changes in latency library.?
Regards,
Reshma
