From: Jakub Kicinski <kuba@kernel.org>
To: David Arinzon <darinzon@amazon.com>,
"Machnikowski, Maciek" <maciek@machnikowski.net>
Cc: David Miller <davem@davemloft.net>, <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.com>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>
Subject: Re: [PATCH v6 net-next 0/4] PHC support in ENA driver
Date: Fri, 7 Feb 2025 16:58:46 -0800 [thread overview]
Message-ID: <20250207165846.53e52bf7@kernel.org> (raw)
In-Reply-To: <20250206141538.549-1-darinzon@amazon.com>
On Thu, 6 Feb 2025 16:15:34 +0200 David Arinzon wrote:
> This patchset adds the support for PHC (PTP Hardware Clock)
> in the ENA driver. The documentation part of the patchset
> includes additional information, including statistics,
> utilization and invocation examples through the testptp
> utility.
Vadim, Maciek, did you see this? Looks like the device has limitations
on number of gettime calls per sec. Could be a good fit for the work
you are prototyping?
next prev parent reply other threads:[~2025-02-08 0:58 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
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 ` Jakub Kicinski [this message]
2025-02-09 12:33 ` [PATCH v6 net-next 0/4] PHC support in ENA driver 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=20250207165846.53e52bf7@kernel.org \
--to=kuba@kernel.org \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=dwmw@amazon.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=maciek@machnikowski.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rrameshbabu@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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).