From: Jakub Kicinski <kuba@kernel.org>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: David Arinzon <darinzon@amazon.com>,
"Machnikowski, Maciek" <maciek@machnikowski.net>,
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>
Subject: Re: [PATCH v6 net-next 0/4] PHC support in ENA driver
Date: Mon, 10 Feb 2025 16:46:26 -0800 [thread overview]
Message-ID: <20250210164626.178efa58@kernel.org> (raw)
In-Reply-To: <7bc5e34e-8be6-46a2-8262-7129fff5e2f3@linux.dev>
On Sun, 9 Feb 2025 12:33:24 +0000 Vadim Fedorenko wrote:
> Yes, we have seen this patchset, and we were thinking of how to
> generalize error_bound property, which was removed from the latest
> version unfortunately. But it's a good point to look at it once
> again in terms of our prototype, thanks!
I was wondering whether they have a user space "time extrapolation
component" which we should try to be compatible with. Perhaps they
just expect that the user will sync system time.
next prev parent reply other threads:[~2025-02-11 0:46 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 ` [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 [this message]
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=20250210164626.178efa58@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 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.