From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Mohsin Bashir <mohsin.bashr@gmail.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
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>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Joshua A Hay <joshua.a.hay@intel.com>
Subject: Re: [PATCH net-next v2 3/7] idpf: support pacing offload
Date: Thu, 23 Jul 2026 17:27:10 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.12dc80a02fdfa@gmail.com> (raw)
In-Reply-To: <d9a1d0c3-c097-42a1-a26d-7291a762390b@gmail.com>
Mohsin Bashir wrote:
>
>
> On 7/22/26 1:43 PM, Willem de Bruijn wrote:
> > From: Willem de Bruijn <willemb@google.com>
> >
> > If skb->tstamp is in the future, program this future delivery txtime
> > in the transmit descriptor.
> >
> > TCP pacing offload is only offloaded if SK_PACING_FQ is negotiated and
> > the FQ offload_horizon is configured.
> >
> > But device support for pacing offload must be more robust. It can also
> > be reached through SO_TXTIME.
> >
> > Bound check txtime. Only packets with timestamp between now and the
> > horizon (max_pacing_offload_horizon) are offloaded.
> >
> > Support only in splitq mode, where tx and tx completion queues are
> > separate and so completions can be returned out of order.
> >
> > Assume that the NIC clock is PTP synchronized to CLOCK_TAI. This
> > can later be refined, e.g., to a custom CLOCK_AUX.
> >
> > Disable if in netpoll. It does not need the feature, and the ktime
> > functions are not safe to call in this context.
> >
> > Cc: Tony Nguyen <anthony.l.nguyen@intel.com>
> > Cc: Joshua A Hay <joshua.a.hay@intel.com>
> > Signed-off-by: Willem de Bruijn <willemb@google.com>
> >
> > @@ -2408,9 +2410,13 @@ void idpf_tx_splitq_build_flow_desc(union idpf_tx_flex_desc *desc,
> > struct idpf_tx_splitq_params *params,
> > u16 td_cmd, u16 size)
> > {
> > - *(u32 *)&desc->flow.qw1.cmd_dtype = (u8)(params->dtype | td_cmd);
> > + *(__le32 *)&desc->flow.qw1.cmd_dtype = cpu_to_le32((u8)(params->dtype | td_cmd));
>
> Looks like an independent change (potentially a fix)?
I did not seem important enough in practice. I'm not aware of any IDPF
on big endian. But I can pull it out if anyone really prefers it.
next prev parent reply other threads:[~2026-07-23 21:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 20:43 [PATCH net-next v2 0/7] hardware pacing offload Willem de Bruijn
2026-07-22 20:43 ` [PATCH net-next v2 1/7] net: ethtool: add hardware pacing offload support to rings Willem de Bruijn
2026-07-23 14:16 ` Mohsin Bashir
2026-07-23 21:29 ` Willem de Bruijn
2026-07-23 22:11 ` Mohsin Bashir
2026-07-22 20:43 ` [PATCH net-next v2 2/7] net_sched: sch_fq: clear past skb->tstamp if offloading pacing Willem de Bruijn
2026-07-22 20:43 ` [PATCH net-next v2 3/7] idpf: support pacing offload Willem de Bruijn
2026-07-23 14:32 ` Mohsin Bashir
2026-07-23 21:27 ` Willem de Bruijn [this message]
2026-07-22 20:43 ` [PATCH net-next v2 4/7] selftests: drv-net: refactor so_txtime errqueue handling Willem de Bruijn
2026-07-23 14:40 ` Mohsin Bashir
2026-07-22 20:43 ` [PATCH net-next v2 5/7] selftests: drv-net: in so_txtime tell apart sw from hw pacing Willem de Bruijn
2026-07-22 20:43 ` [PATCH net-next v2 6/7] selftests: drv-net: extend so_txtime with hw offload Willem de Bruijn
2026-07-22 20:43 ` [PATCH net-next v2 7/7] net: pktgen: add support for SO_TXTIME Willem de Bruijn
2026-07-23 14:12 ` [PATCH net-next v2 0/7] hardware pacing offload Mohsin Bashir
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=willemdebruijn.kernel.12dc80a02fdfa@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=joshua.a.hay@intel.com \
--cc=kuba@kernel.org \
--cc=mohsin.bashr@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox