From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Harshitha Ramamurthy <hramamurthy@google.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, jeroendb@google.com, andrew+netdev@lunn.ch,
willemb@google.com, ziweixiao@google.com,
pkaligineedi@google.com, yyd@google.com, joshwash@google.com,
shailend@google.com, linux@treblig.org, thostet@google.com,
jfraker@google.com, richardcochran@gmail.com, jdamato@fastly.com,
horms@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 6/8] gve: Add rx hardware timestamp expansion
Date: Sat, 24 May 2025 22:59:28 +0100 [thread overview]
Message-ID: <3ca312c2-6749-45a8-b971-2cd0a1a0781a@linux.dev> (raw)
In-Reply-To: <20250522235737.1925605-7-hramamurthy@google.com>
On 23/05/2025 00:57, Harshitha Ramamurthy wrote:
> From: John Fraker <jfraker@google.com>
>
> Allow the rx path to recover the high 32 bits of the full 64 bit rx
> timestamp.
>
> Use the low 32 bits of the last synced nic time and the 32 bits of the
> timestamp provided in the rx descriptor to generate a difference, which
> is then applied to the last synced nic time to reconstruct the complete
> 64-bit timestamp.
>
> This scheme remains accurate as long as no more than ~2 seconds have
> passed between the last read of the nic clock and the timestamping
> application of the received packet.
>
> Signed-off-by: John Fraker <jfraker@google.com>
> Signed-off-by: Ziwei Xiao <ziweixiao@google.com>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> Signed-off-by: Harshitha Ramamurthy <hramamurthy@google.com>
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-05-24 21:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 23:57 [PATCH net-next v3 0/8] gve: Add Rx HW timestamping support Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 1/8] gve: Add device option for nic clock synchronization Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 2/8] gve: Add adminq command to report nic timestamp Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 3/8] gve: Add initial PTP device support Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 4/8] gve: Add adminq lock for queues creation and destruction Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 5/8] gve: Add support to query the nic clock Harshitha Ramamurthy
2025-05-24 21:58 ` Vadim Fedorenko
2025-05-28 2:12 ` Jakub Kicinski
2025-05-28 16:56 ` Ziwei Xiao
2025-05-22 23:57 ` [PATCH net-next v3 6/8] gve: Add rx hardware timestamp expansion Harshitha Ramamurthy
2025-05-24 21:59 ` Vadim Fedorenko [this message]
2025-05-22 23:57 ` [PATCH net-next v3 7/8] gve: Implement ndo_hwtstamp_get/set for RX timestamping Harshitha Ramamurthy
2025-05-22 23:57 ` [PATCH net-next v3 8/8] gve: Advertise support for rx hardware timestamping Harshitha Ramamurthy
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=3ca312c2-6749-45a8-b971-2cd0a1a0781a@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=jdamato@fastly.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=richardcochran@gmail.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 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.