From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Cc: "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
"Reshma Pattan" <reshma.pattan@intel.com>
Subject: RE: [PATCH v4 3/6] latencystats: do not use floating point
Date: Fri, 19 Apr 2024 20:49:56 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F3CE@smartserver.smartshare.dk> (raw)
In-Reply-To: <20240419172926.55447-4-stephen@networkplumber.org>
> + if (unlikely(first_sample)) {
> + first_sample = false;
> +
> glob_stats->min_latency = latency;
> - else if (latency > glob_stats->max_latency)
> glob_stats->max_latency = latency;
> - /*
> - * The average latency is measured using exponential moving
> - * average, i.e. using EWMA
> - * https://en.wikipedia.org/wiki/Moving_average
> - */
> - glob_stats->avg_latency +=
> - alpha * (latency - glob_stats->avg_latency);
> + glob_stats->avg_latency = latency;
> + glob_stats->jitter = latency / 2;
Setting jitter at first sample as latency / 2 is wrong.
Jitter should remain zero at first sample.
> + } else {
> + /*
> + * The jitter is calculated as statistical mean of
> interpacket
> + * delay variation. The "jitter estimate" is computed
> by taking
> + * the absolute values of the ipdv sequence and
> applying an
> + * exponential filter with parameter 1/16 to generate
> the
> + * estimate. i.e J=J+(|D(i-1,i)|-J)/16. Where J is
> jitter,
> + * D(i-1,i) is difference in latency of two
> consecutive packets
> + * i-1 and i.
> + * Reference: Calculated as per RFC 5481, sec 4.1,
> + * RFC 3393 sec 4.5, RFC 1889 sec.
> + */
> + glob_stats->jitter += ((prev_latency - latency)
> + - glob_stats->jitter) / 16;
With jitter remaining zero at first sample,
Acked-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2024-04-19 18:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 19:50 [RFC] latencystats: performance overhaul Stephen Hemminger
2024-04-08 21:26 ` [PATCH v2] " Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 0/6] latencystats: cleanup Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 1/6] latencystats: replace use of VLA Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 2/6] latencystats: handle fractional cycles per ns Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 3/6] latencystats: do not use floating point Stephen Hemminger
2024-04-19 18:49 ` Morten Brørup [this message]
2024-04-19 22:45 ` Stephen Hemminger
2024-04-20 7:31 ` Morten Brørup
2024-04-19 17:28 ` [PATCH v4 4/6] latencystats: fix log messages Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 5/6] latencystats: update include files Stephen Hemminger
2024-04-19 17:28 ` [PATCH v4 6/6] latencystats: fix for pedantic warnings Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 0/9] latencystats: improve algorithms and tests Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 1/9] latencystats: replace use of VLA Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 2/9] latencystats: handle fractional cycles per ns Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 3/9] latencystats: do not use floating point Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 4/9] latencystats: fix log messages Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 5/9] latencystats: update include files Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 6/9] latencystats: enforce that unused callback function is NULL Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 7/9] latencystats: add metric for number of samples Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 8/9] test: use initialization in latencystats test Stephen Hemminger
2024-04-22 15:21 ` [PATCH v5 9/9] test: add more latencystats tests Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 0/8] latencystats: improvements to algorithm and test Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 1/8] latencystats: replace use of VLA Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 2/8] latencystats: handle fractional cycles per ns Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 3/8] latencystats: do not use floating point Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 4/8] latencystats: fix log messages Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 5/8] latencystats: update include files Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 6/8] latencystats: enforce that unused callback function is NULL Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 7/8] latencystats: add metric for number of samples Stephen Hemminger
2024-05-29 22:54 ` [PATCH v6 8/8] test: update to latencystats tests Stephen Hemminger
2024-07-04 15:21 ` [PATCH v6 0/8] latencystats: improvements to algorithm and test David Marchand
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=98CBD80474FA8B44BF855DF32C47DC35E9F3CE@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.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).