From: "Bernstein, Amit" <amitbern@amazon.com>
To: "tglx@linutronix.de" <tglx@linutronix.de>,
"richardcochran@gmail.com" <richardcochran@gmail.com>
Cc: "kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Dagan, Noam" <ndagan@amazon.com>,
"Arinzon, David" <darinzon@amazon.com>,
"Agroskin, Shay" <shayagr@amazon.com>
Subject: Add PHC support with error bound value for ENA driver
Date: Thu, 1 Feb 2024 07:24:51 +0000 [thread overview]
Message-ID: <8803342f01f54ca38296cedafea10bde@amazon.com> (raw)
Hi Thomas, Richard and all,
In one of the upcoming releases, we're planning to add PHC support to the ENA driver (/drivers/net/ethernet/amazon/ena/)
To provide the best experience for service customers, the ENA driver will expose an error_bound parameter (expressed in nanoseconds),
which will represent the maximal clock error on each given PHC timestamp.
The error bound is calculated by the device, taking into account the accuracy and delays of all the device's PHC components.
Based on our search, there is no similar functionality in other drivers, meaning there is no user interface to expose it.
We're currently exploring the best method of exposing this capability to the user.
Our debate is between:
- Extending the gettimex64 API in ptp_clock_info
- Introducing a new devlink entry
- Updating the time-related ethtool option (-T flag).
As our device sends each PHC timestamp with an error_bound value together, gettimex64 is the reasonable option for us and our recommended solution.
We would like to ask for your recommendation.
We have already consulted with Jakub, who recommended that we consult with all of you.
For more information, you may visit: https://aws.amazon.com/blogs/compute/its-about-time-microsecond-accurate-clocks-on-amazon-ec2-instances/
Thanks,
Amit
next reply other threads:[~2024-02-01 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 7:24 Bernstein, Amit [this message]
2024-02-01 14:49 ` Add PHC support with error bound value for ENA driver Richard Cochran
2024-02-01 18:56 ` Bernstein, Amit
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=8803342f01f54ca38296cedafea10bde@amazon.com \
--to=amitbern@amazon.com \
--cc=darinzon@amazon.com \
--cc=kuba@kernel.org \
--cc=ndagan@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=shayagr@amazon.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.