DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v7 0/2] net/af_xdp: add Rx timestamping and read_clock support
Date: Wed, 19 Aug 2026 13:20:32 -0700	[thread overview]
Message-ID: <20260819132032.0c606bb3@phoenix.local> (raw)
In-Reply-To: <20260818065000.1597610-1-blasko@google.com>

On Tue, 18 Aug 2026 06:49:57 +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.
> ---

Applied to next-net.
Had to fix some merge conflicts with the previous path changes.

      parent reply	other threads:[~2026-08-19 20:20 UTC|newest]

Thread overview: 32+ 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   ` [PATCH v4 0/2] net/af_xdp: add Rx timestamping and read_clock support Stephen Hemminger
2026-08-12 23:36 ` [PATCH v5 " Mark Blasko
2026-08-12 23:36   ` [PATCH v5 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-08-12 23:36   ` [PATCH v5 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-08-13  2:56   ` [PATCH v5 0/2] net/af_xdp: add Rx timestamping and read_clock support Stephen Hemminger
2026-08-15  0:45 ` [PATCH v6 " Mark Blasko
2026-08-15  0:45   ` [PATCH v6 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-08-15  0:45   ` [PATCH v6 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-08-15 15:42   ` [PATCH v6 0/2] net/af_xdp: add Rx timestamping and read_clock support Stephen Hemminger
2026-08-18  6:49 ` [PATCH v7 " Mark Blasko
2026-08-18  6:49   ` [PATCH v7 1/2] net/af_xdp: add af_xdp rx metadata and dynamic timestamping support Mark Blasko
2026-08-18  6:49   ` [PATCH v7 2/2] net/af_xdp: add read_clock support to AF_XDP PMD Mark Blasko
2026-08-19 20:20   ` 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=20260819132032.0c606bb3@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