From: Jakub Kicinski <kuba@kernel.org>
To: "Arinzon, David" <darinzon@amazon.com>
Cc: David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Richard Cochran <richardcochran@gmail.com>,
"Woodhouse, David" <dwmw@amazon.co.uk>,
"Machulsky, Zorik" <zorik@amazon.com>,
"Matushevsky, Alexander" <matua@amazon.com>,
"Bshara, Saeed" <saeedb@amazon.com>,
"Wilson, Matt" <msw@amazon.com>,
"Liguori, Anthony" <aliguori@amazon.com>,
"Bshara, Nafea" <nafea@amazon.com>,
"Schmeilin, Evgeny" <evgenys@amazon.com>,
"Belgazal, Netanel" <netanel@amazon.com>,
"Saidi, Ali" <alisaidi@amazon.com>,
"Herrenschmidt, Benjamin" <benh@amazon.com>,
"Kiyanovski, Arthur" <akiyano@amazon.com>,
"Dagan, Noam" <ndagan@amazon.com>,
"Bernstein, Amit" <amitbern@amazon.com>,
"Agroskin, Shay" <shayagr@amazon.com>,
"Abboud, Osama" <osamaabb@amazon.com>,
"Ostrovsky, Evgeny" <evostrov@amazon.com>,
"Tabachnik, Ofir" <ofirt@amazon.com>,
"Machnikowski, Maciek" <maciek@machnikowski.net>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>,
Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH v6 net-next 3/4] net: ena: Add PHC documentation
Date: Mon, 10 Feb 2025 16:43:58 -0800 [thread overview]
Message-ID: <20250210164358.11091722@kernel.org> (raw)
In-Reply-To: <01fd0c4d50c7493986d80e22b0506fdf@amazon.com>
On Mon, 10 Feb 2025 15:28:19 +0000 Arinzon, David wrote:
> You are right in the regard that it is not a network specific functionality.
> Having said that, PHC is a network card capability, making it a network-related component rather than purely a timekeeping feature.
> Moreover we failed to find an existing tool which would allow users to get valuable feedback of the system's overall health.
>
> Researching its existing support in the kernel we noted that:
> - PHC is embedded in network NIC and is supported by multiple NIC vendors in the kernel
> - PHC information is visible through ethtool -T
> - The Linux networking stack uses PHC for timekeeping as well as for packet timestamping (via SO_TIMESTAMPING).
> Packet timestamping statistics are available through ethtool get_ts_stats hook
>
> We have found `ethtool -S` as a suitable location for exposing these statistics, which are unique to the ENA NIC.
>
> We'd appreciate your thoughts on the matter, is there an alternative tool you can recommend?
We try to steer folks towards read-only debugfs files for stuff
that's not strictly networking related. You also add a custom
sysfs file in patch 4, I reckon adding stats there may also be
a natural place for the user?
Patch 4 FWIW is lacking slightly in the justification, would
be good to clarify why it's disabled by default. Single sentence
of "why" would be great.
next prev parent reply other threads:[~2025-02-11 0:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 14:15 [PATCH v6 net-next 0/4] PHC support in ENA driver David Arinzon
2025-02-06 14:15 ` [PATCH v6 net-next 1/4] net: ena: Add PHC support in the " David Arinzon
2025-02-08 0:54 ` Jakub Kicinski
2025-02-06 14:15 ` [PATCH v6 net-next 2/4] net: ena: PHC silent reset David Arinzon
2025-02-06 14:15 ` [PATCH v6 net-next 3/4] net: ena: Add PHC documentation David Arinzon
2025-02-08 0:55 ` Jakub Kicinski
2025-02-10 15:28 ` Arinzon, David
2025-02-11 0:43 ` Jakub Kicinski [this message]
2025-02-11 6:41 ` Arinzon, David
2025-02-06 14:15 ` [PATCH v6 net-next 4/4] net: ena: PHC enable through sysfs David Arinzon
2025-02-08 0:58 ` [PATCH v6 net-next 0/4] PHC support in ENA driver Jakub Kicinski
2025-02-09 12:33 ` Vadim Fedorenko
2025-02-11 0:46 ` Jakub Kicinski
2025-02-11 7:58 ` Maciek Machnikowski
2025-02-14 9:57 ` [EXTERNAL] " David Woodhouse
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=20250210164358.11091722@kernel.org \
--to=kuba@kernel.org \
--cc=akiyano@amazon.com \
--cc=aliguori@amazon.com \
--cc=alisaidi@amazon.com \
--cc=amitbern@amazon.com \
--cc=benh@amazon.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.co.uk \
--cc=edumazet@google.com \
--cc=evgenys@amazon.com \
--cc=evostrov@amazon.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=maciek@machnikowski.net \
--cc=matua@amazon.com \
--cc=msw@amazon.com \
--cc=nafea@amazon.com \
--cc=ndagan@amazon.com \
--cc=netanel@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=ofirt@amazon.com \
--cc=osamaabb@amazon.com \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=saeedb@amazon.com \
--cc=shayagr@amazon.com \
--cc=zorik@amazon.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;
as well as URLs for NNTP newsgroup(s).