From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: netdev@vger.kernel.org, Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH net-next v2] wireguard: queuing: preserve napi_id on decapsulation
Date: Tue, 4 Nov 2025 10:28:19 +0100 [thread overview]
Message-ID: <aQnHMyJYU4kuCWCf@localhost> (raw)
In-Reply-To: <CAHmME9qcj=zHHm0-gTeSLxqwufEBFO721ciYQODTws6wTb7+Rg@mail.gmail.com>
On Mon, Nov 03, 2025 at 05:00:19PM +0100, Jason A. Donenfeld wrote:
> On Mon, Nov 3, 2025 at 11:34 AM Miroslav Lichvar <mlichvar@redhat.com> wrote:
> > + } else {
> > +#ifdef CONFIG_NET_RX_BUSY_POLL
> > + skb->napi_id = napi_id;
> > +#endif
>
> It looks like io_uring has timestamping on tx, not just rx:
> SOCKET_URING_OP_TX_TIMESTAMP -> io_uring_cmd_timestamp ->
> io_process_timestamp_skb -> skb_get_tx_timestamp -> skb_napi_id
That doesn't seem to be reachable. skb_get_tx_timestamp() calls
get_timestamp()->skb_napi_id() only when the SKBTX_HW_TSTAMP_NETDEV
flag is set, which is done only by two drivers (tsnep, igc) and only
in the RX path. Using a tx_flags field for RX is slightly confusing.
> So are you sure this should be in an `else {` block?
Yes, at least for the use case with the timestamping option I'm trying
to fix. If it was outside of the else block, it would be copying the
sender_cpu field of the union (used by XPS). Maybe it would make sense
to do that too, I know nothing about XPS, but in that case the value
shouldn't be read by skb_napi_id(), which is enabled only by
CONFIG_NET_RX_BUSY_POLL.
--
Miroslav Lichvar
prev parent reply other threads:[~2025-11-04 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 10:34 [PATCH net-next v2] wireguard: queuing: preserve napi_id on decapsulation Miroslav Lichvar
2025-11-03 16:00 ` Jason A. Donenfeld
2025-11-04 9:28 ` Miroslav Lichvar [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=aQnHMyJYU4kuCWCf@localhost \
--to=mlichvar@redhat.com \
--cc=Jason@zx2c4.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).