From: Pavel Begunkov <asml.silence@gmail.com>
To: lollipopkit <a@lolli.tech>, Jens Axboe <axboe@kernel.dk>
Cc: Willem de Bruijn <willemb@google.com>,
io-uring@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] io_uring/cmd_net: end TX_TIMESTAMP multishot when the CQ is full
Date: Sun, 27 Sep 2026 20:16:16 +0100 [thread overview]
Message-ID: <e2e61157-896f-46a2-8c85-8e64b4cdb004@gmail.com> (raw)
In-Reply-To: <20260927074206.65427-1-a@lolli.tech>
On 9/27/26 08:42, lollipopkit wrote:
> SOCKET_URING_OP_TX_TIMESTAMP arms an EPOLLERR apoll multishot and, on
> each error queue edge, posts one 32 byte aux CQE per timestamp skb. Aux
> CQEs have no overflow backing, so io_uring_cmd_post_mshot_cqe32() fails
> once the CQ ring is full. The loop then stops, splices the unprocessed
> skbs back onto sk_error_queue and returns -EAGAIN.
...> static int io_uring_cmd_timestamp(struct socket *sock,
> @@ -135,7 +137,8 @@ static int io_uring_cmd_timestamp(struct socket *sock,
> skb = skb_peek(&list);
> if (!skb)
> break;
> - if (!io_process_timestamp_skb(cmd, sk, skb, issue_flags))
> + ret = io_process_timestamp_skb(cmd, sk, skb, issue_flags);
> + if (ret)
> break;
> __skb_dequeue(&list);
> consume_skb(skb);
> @@ -145,6 +148,12 @@ static int io_uring_cmd_timestamp(struct socket *sock,
> scoped_guard(spinlock_irqsave, &q->lock)
> skb_queue_splice(&list, q);
> }
> + /*
> + * Aux CQEs cannot overflow and the poll is edge triggered, so nothing
> + * re-runs the command once the CQ drains. End the multishot instead.
> + */
> + if (ret == -ENOBUFS)
> + return -ENOBUFS;
I'd make it a 3-state return instead of relying on
skb_get_tx_timestamp() not returning specific error codes, but it
should be fine for now.
Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>
> return -EAGAIN;
> }
>
>
> base-commit: a3bdf68feecc57af5c11fb599f860ac9790ffad9
--
Pavel Begunkov
next prev parent reply other threads:[~2026-09-27 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 7:42 lollipopkit
2026-09-27 19:16 ` Pavel Begunkov [this message]
2026-09-28 14:31 ` Jens Axboe
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=e2e61157-896f-46a2-8c85-8e64b4cdb004@gmail.com \
--to=asml.silence@gmail.com \
--cc=a@lolli.tech \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®