doc: update timestamp validity for latency measurement
Checks
Commit Message
Updated the doc on how packets are marked to identify
their timestamp as valid and considered for latency
measurement.
Suggested-by: Bao-Long Tran <longtb5@viettel.com.vn>
Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
---
This change is relevant to the below patch and must be applied
after that.
http://patches.dpdk.org/patch/45328/
---
doc/guides/prog_guide/metrics_lib.rst | 9 +++++++++
1 file changed, 9 insertions(+)
Comments
> Updated the doc on how packets are marked to identify their timestamp as
> valid and considered for latency measurement.
>
> Suggested-by: Bao-Long Tran <longtb5@viettel.com.vn>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
>
> +Timestamp and latency calculation
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +The Latency stats library marks the time in the timestamp field of the
> +mbuf for the ingress packets and sets the ``PKT_RX_TIMESTAMP`` flag of
> +``ol_flags`` for the mbuf to indicate the marked time as a valid one.
> +At the egress, the mbufs with the flag set are considered having valid
> +timestamp and are used for the latency calculation.
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
04/10/2018 14:23, Reshma Pattan:
> Updated the doc on how packets are marked to identify
> their timestamp as valid and considered for latency
> measurement.
>
> Suggested-by: Bao-Long Tran <longtb5@viettel.com.vn>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> This change is relevant to the below patch and must be applied
> after that.
> http://patches.dpdk.org/patch/45328/
It's better to squash doc & code patches together, when possible.
Applied, thanks
@@ -271,3 +271,12 @@ de-initialise the latency library.
.. code-block:: c
rte_latencystats_uninit();
+
+Timestamp and latency calculation
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The Latency stats library marks the time in the timestamp field of the
+mbuf for the ingress packets and sets the ``PKT_RX_TIMESTAMP`` flag of
+``ol_flags`` for the mbuf to indicate the marked time as a valid one.
+At the egress, the mbufs with the flag set are considered having valid
+timestamp and are used for the latency calculation.