From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Ziwei Xiao <ziweixiao@google.com>
Cc: Harshitha Ramamurthy <hramamurthy@google.com>,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, jeroendb@google.com,
andrew+netdev@lunn.ch, willemb@google.com,
pkaligineedi@google.com, yyd@google.com, joshwash@google.com,
shailend@google.com, linux@treblig.org, thostet@google.com,
jfraker@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/6] gve: Add Rx HW timestamping support
Date: Wed, 23 Apr 2025 22:06:22 +0100 [thread overview]
Message-ID: <99b52c22-c797-4291-92ad-39eaf041ae8c@linux.dev> (raw)
In-Reply-To: <CAG-FcCN-a_v33_d_+qLSqVy+heACB5JcXtiBXP63Q1DyZU+5vw@mail.gmail.com>
On 23/04/2025 21:46, Ziwei Xiao wrote:
> On Wed, Apr 23, 2025 at 3:13 AM Vadim Fedorenko
> <vadim.fedorenko@linux.dev> wrote:
>>
>> On 18/04/2025 23:12, Harshitha Ramamurthy wrote:
>>> From: Ziwei Xiao <ziweixiao@google.com>
>>>
>>> This patch series add the support of Rx HW timestamping, which sends
>>> adminq commands periodically to the device for clock synchronization with
>>> the nic.
>>
>> It looks more like other PHC devices, but no PTP clock is exported. Do
>> you plan to implement TX HW timestamps for this device later?
>> Is it possible to use timecounter to provide proper PTP device on top of
>> GVE?
> Yes, the TX HW timestamps and PTP device work is undergoing. Those
> would be sent out in separate patch series when they are ready.
It looks like it's better to have PTP device ready firts as it
definitely needs some worker to keep time counting. And it should be
done with ptp::aux_work and replace the work you introduced in patch 3
of this series.
>>
>>>
>>> John Fraker (5):
>>> gve: Add device option for nic clock synchronization
>>> gve: Add adminq command to report nic timestamp.
>>> gve: Add rx hardware timestamp expansion
>>> gve: Add support for SIOC[GS]HWTSTAMP IOCTLs
>>> gve: Advertise support for rx hardware timestamping
>>>
>>> Kevin Yang (1):
>>> gve: Add initial gve_clock
>>>
>>> drivers/net/ethernet/google/gve/Makefile | 2 +-
>>> drivers/net/ethernet/google/gve/gve.h | 14 +++
>>> drivers/net/ethernet/google/gve/gve_adminq.c | 51 ++++++++-
>>> drivers/net/ethernet/google/gve/gve_adminq.h | 26 +++++
>>> drivers/net/ethernet/google/gve/gve_clock.c | 103 ++++++++++++++++++
>>> .../net/ethernet/google/gve/gve_desc_dqo.h | 3 +-
>>> drivers/net/ethernet/google/gve/gve_ethtool.c | 23 +++-
>>> drivers/net/ethernet/google/gve/gve_main.c | 47 ++++++++
>>> drivers/net/ethernet/google/gve/gve_rx_dqo.c | 26 +++++
>>> 9 files changed, 290 insertions(+), 5 deletions(-)
>>> create mode 100644 drivers/net/ethernet/google/gve/gve_clock.c
>>>
>>
next prev parent reply other threads:[~2025-04-23 21:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 22:12 [PATCH net-next 0/6] gve: Add Rx HW timestamping support Harshitha Ramamurthy
2025-04-18 22:12 ` [PATCH net-next 1/6] gve: Add device option for nic clock synchronization Harshitha Ramamurthy
2025-04-23 1:42 ` Joe Damato
2025-04-18 22:12 ` [PATCH net-next 2/6] gve: Add adminq command to report nic timestamp Harshitha Ramamurthy
2025-04-23 1:44 ` Joe Damato
2025-04-18 22:12 ` [PATCH net-next 3/6] gve: Add initial gve_clock Harshitha Ramamurthy
2025-04-23 1:49 ` Joe Damato
2025-04-18 22:12 ` [PATCH net-next 4/6] gve: Add rx hardware timestamp expansion Harshitha Ramamurthy
2025-04-23 1:21 ` Joe Damato
2025-04-24 18:40 ` Ziwei Xiao
2025-04-18 22:12 ` [PATCH net-next 5/6] gve: Add support for SIOC[GS]HWTSTAMP IOCTLs Harshitha Ramamurthy
2025-04-23 1:52 ` Joe Damato
2025-04-18 22:12 ` [PATCH net-next 6/6] gve: Advertise support for rx hardware timestamping Harshitha Ramamurthy
2025-04-23 1:53 ` Joe Damato
2025-04-23 10:13 ` [PATCH net-next 0/6] gve: Add Rx HW timestamping support Vadim Fedorenko
2025-04-23 20:46 ` Ziwei Xiao
2025-04-23 21:06 ` Vadim Fedorenko [this message]
2025-04-23 22:56 ` Jakub Kicinski
2025-04-24 18:39 ` Ziwei Xiao
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=99b52c22-c797-4291-92ad-39eaf041ae8c@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=jfraker@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=shailend@google.com \
--cc=thostet@google.com \
--cc=willemb@google.com \
--cc=yyd@google.com \
--cc=ziweixiao@google.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