From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, andrew@lunn.ch,
Willem de Bruijn <willemb@google.com>
Subject: [PATCH net-next 0/7] hardware pacing offload
Date: Mon, 6 Jul 2026 09:34:02 -0400 [thread overview]
Message-ID: <20260706133433.3142805-1-willemdebruijn.kernel@gmail.com> (raw)
From: Willem de Bruijn <willemb@google.com>
Enable safe hardware pacing offload on a first device (idpf), plus support.
- Add ethtool support for admin control over the device feature
- Add device support to the idpf driver
Besides the main feature, also
- Small optimization to FQ offload: avoid unnecessary ktime_.._get().
- Expand so_txtime drv-net test with hw offload testcases.
- Expand pktgen with txtime feature.
Details in the individual patches.
Willem de Bruijn (7):
net: ethtool: add hardware pacing offload support to rings
net_sched: sch_fq: clear past skb->tstamp if offloading pacing
idpf: support pacing offload
selftests: drv-net: refactor so_txtime errqueue handling
selftests: drv-net: in so_txtime tell apart sw from hw pacing
selftests: drv-net: extend so_txtime with hw offload
net: pktgen: add support for SO_TXTIME
Documentation/netlink/specs/ethtool.yaml | 6 +
.../networking/net_cachelines/net_device.rst | 3 +-
.../net/ethernet/intel/idpf/idpf_ethtool.c | 3 +-
drivers/net/ethernet/intel/idpf/idpf_lib.c | 5 +
drivers/net/ethernet/intel/idpf/idpf_txrx.c | 63 +++++++-
drivers/net/ethernet/intel/idpf/idpf_txrx.h | 2 +
include/linux/ethtool.h | 6 +
include/linux/netdevice.h | 6 +-
.../uapi/linux/ethtool_netlink_generated.h | 2 +
net/core/pktgen.c | 85 ++++++++++
net/core/rtnetlink.c | 2 +-
net/ethtool/common.c | 3 +
net/ethtool/netlink.h | 2 +-
net/ethtool/rings.c | 30 +++-
net/sched/sch_fq.c | 21 ++-
tools/testing/selftests/drivers/net/settings | 1 +
.../testing/selftests/drivers/net/so_txtime.c | 147 +++++++++++++-----
.../selftests/drivers/net/so_txtime.py | 72 ++++++++-
18 files changed, 399 insertions(+), 60 deletions(-)
create mode 100644 tools/testing/selftests/drivers/net/settings
--
2.55.0.795.g602f6c329a-goog
next reply other threads:[~2026-07-06 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 13:34 Willem de Bruijn [this message]
2026-07-06 13:34 ` [PATCH net-next 1/7] net: ethtool: add hardware pacing offload support to rings Willem de Bruijn
2026-07-06 13:34 ` [PATCH net-next 2/7] net_sched: sch_fq: clear past skb->tstamp if offloading pacing Willem de Bruijn
2026-07-06 13:34 ` [PATCH net-next 3/7] idpf: support pacing offload Willem de Bruijn
2026-07-10 15:04 ` Paolo Abeni
2026-07-10 21:37 ` Tony Nguyen
2026-07-11 20:13 ` Willem de Bruijn
2026-07-06 13:34 ` [PATCH net-next 4/7] selftests: drv-net: refactor so_txtime errqueue handling Willem de Bruijn
2026-07-06 13:34 ` [PATCH net-next 5/7] selftests: drv-net: in so_txtime tell apart sw from hw pacing Willem de Bruijn
2026-07-06 13:34 ` [PATCH net-next 6/7] selftests: drv-net: extend so_txtime with hw offload Willem de Bruijn
2026-07-10 15:26 ` Paolo Abeni
2026-07-06 13:34 ` [PATCH net-next 7/7] net: pktgen: add support for SO_TXTIME Willem de Bruijn
2026-07-10 15:20 ` Paolo Abeni
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=20260706133433.3142805-1-willemdebruijn.kernel@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@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.