From: Stephen Hemminger <stephen@networkplumber.org>
To: Mark Blasko <blasko@google.com>
Cc: dev@dpdk.org, ciara.loftus@intel.com, mtahhan@redhat.com,
joshwash@google.com, jtranoleary@google.com
Subject: Re: [PATCH v4 0/2] net/af_xdp: add Rx timestamping and read_clock support
Date: Sat, 1 Aug 2026 08:49:20 -0700 [thread overview]
Message-ID: <20260801084920.4538596b@phoenix.local> (raw)
In-Reply-To: <20260801032534.2865192-1-blasko@google.com>
On Sat, 1 Aug 2026 03:25:31 +0000
Mark Blasko <blasko@google.com> wrote:
> This patch series introduces support for dynamic RX timestamping and
> clock querying in the AF_XDP Poll Mode Driver.
>
> The first patch introduces three new vdev devargs to specify
> layout-agnostic metadata offsets and bitmasks for extracting hardware
> RX timestamps from XDP metadata into the mbuf dynamic timestamp field.
>
> The second patch implements the read_clock ethdev operation, querying
> ethtool for the interface's PTP Hardware Clock index at start and using
> clock_gettime to query the NIC hardware clock time.
> ---
AI review with Claude Opus sees some valid issues:
The significant one is in patch 1: rx_timestamp_enabled is computed in
eth_rx_queue_setup() and includes timestamp_dynfield_offset >= 0, but
the dynfield is only registered in eth_dev_start(), which runs
afterwards. Since af_xdp doesn't advertise runtime queue setup, the
flag is latched false and timestamps are never written. af_packet has
the same start-time registration but keeps the offset out of the enable
condition — setting the flag from rxmode.offloads in
eth_dev_configure() is the fix.
Second error: the release notes hunks target release_26_07.rst, but
main is 26.11.0-rc0 and 26.07 has shipped — that's also why the series
no longer applies.
Beyond that, mostly documentation/code mismatches: parse_hex_arg() is
base-16 only while the doc promises hex or decimal, the offset
direction is undocumented (they're measured backwards from mtod), and
the doc's own example puts the validity byte inside the timestamp bytes.
prev parent reply other threads:[~2026-08-01 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 21:53 [PATCH] net/af_xdp: add Rx metadata and dynamic timestamping support Mark Blasko
2026-06-23 22:06 ` Stephen Hemminger
2026-06-29 0:50 ` Mark Blasko
2026-06-29 17:38 ` Stephen Hemminger
2026-06-29 19:10 ` Joshua Washington
2026-06-29 20:02 ` Stephen Hemminger
2026-06-29 20:03 ` Stephen Hemminger
2026-06-30 0:41 ` Joshua Washington
2026-07-10 22:10 ` [PATCH v2 0/2] net/af_xdp: add Rx timestamping and read_clock support Mark Blasko
2026-07-10 22:10 ` [PATCH v2 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-07-10 22:10 ` [PATCH v2 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-07-21 12:11 ` [PATCH v3 0/2] net/af_xdp: add Rx timestamping and read_clock support Mark Blasko
2026-07-21 12:11 ` [PATCH v3 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-07-26 17:01 ` Stephen Hemminger
2026-08-01 3:26 ` Mark Blasko
2026-07-21 12:11 ` [PATCH v3 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-08-01 3:25 ` [PATCH v4 0/2] net/af_xdp: add Rx timestamping and read_clock support Mark Blasko
2026-08-01 3:25 ` [PATCH v4 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-08-01 3:25 ` [PATCH v4 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-08-01 15:49 ` Stephen Hemminger [this message]
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=20260801084920.4538596b@phoenix.local \
--to=stephen@networkplumber.org \
--cc=blasko@google.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=joshwash@google.com \
--cc=jtranoleary@google.com \
--cc=mtahhan@redhat.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