From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC v3] latencystats: added new library for latency stats
Date: Tue, 18 Oct 2016 10:44:43 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F010AF910@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1476711584-25377-1-git-send-email-reshma.pattan@intel.com>
Hi,
The below latency stats RFC adds new field to second cache line of mbuf. This is not an ABI break.
But I would like to emphasize on this point so you can have a look into the changes and provide comments.
Thanks,
Reshma
> -----Original Message-----
> From: Pattan, Reshma
> Sent: Monday, October 17, 2016 2:40 PM
> To: dev@dpdk.org
> Cc: Pattan, Reshma <reshma.pattan@intel.com>
> Subject: [RFC v3] latencystats: added new library for latency stats
>
> Library is designed to calculate latency stats and report them to the application
> when queried. Library measures minimum, average, maximum latencies and
> jitter in nano seconds.
> Current implementation supports global latency stats, i.e. per application stats.
>
> Added new field to mbuf struct to mark the packet arrival time on Rx and use the
> times tamp to measure the latency on Tx.
>
> Modified dpdk-procinfo process to display the new stats.
>
> APIs:
>
> Added APIs to initialize and un initialize latency stats calculation.
> Added API to retrieve latency stats names and values.
>
> Functionality:
>
> *Library will register ethdev Rx/Tx callbacks for each active port, queue
> combinations.
> *Library will register latency stats names with new stats library, which is under
> design for now.
> *Rx packets will be marked with time stamp on each sampling interval.
> *On Tx side, packets with time stamp will be considered for calculating the
> minimum, maximum, average latencies and jitter.
> *Average latency is calculated by summing all the latencies measured for each
> time stamped packet and dividing that by total time stamped packets.
> *Minimum and maximum latencies will be low and high latency values observed
> so far.
> *Jitter calculation is done based on inter packet delay variation.
> *Measured stats can be retrieved via get API of the libray (or) by calling generic
> get API of the new stats library, in this case callback is provided to update the
> stats into new stats library.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2016-10-18 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 16:39 [dpdk-dev] [RFC] " Reshma Pattan
2016-10-07 16:10 ` [dpdk-dev] [RFC v2] " Reshma Pattan
2016-10-17 13:39 ` [dpdk-dev] [RFC v3] " Reshma Pattan
2016-10-18 10:44 ` Pattan, Reshma [this message]
2016-11-07 13:14 ` [dpdk-dev] [PATCH v4] " Reshma Pattan
2016-11-08 12:34 ` Pattan, Reshma
2016-11-11 2:22 ` Remy Horton
2016-11-11 11:15 ` Pattan, Reshma
2016-11-15 13:37 ` [dpdk-dev] [PATCH v5] " Reshma Pattan
2016-11-18 6:17 ` Remy Horton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3AEA2BF9852C6F48A459DA490692831F010AF910@IRSMSX109.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).