From: Miroslav Lichvar <mlichvar@redhat.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: kurt@linutronix.de, anthony.l.nguyen@intel.com,
intel-wired-lan@lists.osuosl.org, vladimir.oltean@nxp.com
Subject: Re: [Intel-wired-lan] [PATCH iwl-net v3 3/4] igc: Retrieve TX timestamp during interrupt handling
Date: Tue, 6 Jun 2023 09:08:00 +0200 [thread overview]
Message-ID: <ZH7bUKKxocyhajad@localhost> (raw)
In-Reply-To: <20230606013325.602823-4-vinicius.gomes@intel.com>
On Mon, Jun 05, 2023 at 06:33:24PM -0700, Vinicius Costa Gomes wrote:
> After:
>
> $ sudo ./ntpperf -i enp3s0 -m 10:22:22:22:22:21 -d 192.168.1.3 -s 172.18.0.0/16 -I -H -o -37
> | responses | TX timestamp offset (ns)
> rate clients | lost invalid basic xleave | min mean max stddev
> 1000 100 0.00% 0.00% 0.00% 100.00% -44 +0 +61 19
> 1500 150 0.00% 0.00% 0.00% 100.00% -6 +39 +81 16
> 2250 225 0.00% 0.00% 0.00% 100.00% -22 +25 +69 15
> 3375 337 0.00% 0.00% 0.00% 100.00% -28 +15 +56 14
> 5062 506 0.00% 0.00% 0.00% 100.00% +7 +78 +143 27
> 7593 759 0.00% 0.00% 0.00% 100.00% -54 +24 +144 47
> 11389 1138 0.00% 0.00% 0.00% 100.00% -90 -33 +28 21
> 17083 1708 0.00% 0.00% 0.00% 100.00% -50 -2 +35 14
> 25624 2562 0.00% 0.00% 0.00% 100.00% -62 +7 +66 23
> 38436 3843 0.00% 0.00% 0.00% 100.00% -33 +30 +5395 36
> 57654 5765 0.00% 0.00% 100.00% 0.00%
> 86481 8648 0.00% 0.00% 100.00% 0.00%
> 129721 12972 0.00% 0.00% 100.00% 0.00%
Just a comment about this test. The reason why it goes from 100%
xleave to 100% basic is that the number of clients becomes larger than
the number of transmit timestamps that the server can hold. To keep
xleave working at higher rates and see the TX timestamp stats it is
necessary to increase clientloglimit in the server chrony.conf.
--
Miroslav Lichvar
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-06-06 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 1:33 [Intel-wired-lan] [PATCH iwl-net v3 0/4] igc: TX timestamping fixes Vinicius Costa Gomes
2023-06-06 1:33 ` [Intel-wired-lan] [PATCH iwl-net v3 1/4] igc: Fix race condition in PTP tx code Vinicius Costa Gomes
2023-06-06 1:33 ` [Intel-wired-lan] [PATCH iwl-net v3 2/4] igc: Check if hardware TX timestamping is enabled earlier Vinicius Costa Gomes
2023-06-06 1:33 ` [Intel-wired-lan] [PATCH iwl-net v3 3/4] igc: Retrieve TX timestamp during interrupt handling Vinicius Costa Gomes
2023-06-06 7:08 ` Miroslav Lichvar [this message]
2023-06-06 1:33 ` [Intel-wired-lan] [PATCH iwl-net v3 4/4] igc: Add workaround for missing timestamps Vinicius Costa Gomes
2023-06-06 5:07 ` Paul Menzel
2023-06-07 17:29 ` Vinicius Costa Gomes
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=ZH7bUKKxocyhajad@localhost \
--to=mlichvar@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kurt@linutronix.de \
--cc=vinicius.gomes@intel.com \
--cc=vladimir.oltean@nxp.com \
/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