io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET 0/2] Add support for IORING_CQE_F_SOCK_FULL
Date: Wed,  5 Nov 2025 12:30:57 -0700	[thread overview]
Message-ID: <20251105193639.235441-1-axboe@kernel.dk> (raw)

Hi,

It can be useful for userspace to know if a send request had to go
through poll to complete, as that generally means that the socket was
out of space. On the send side, this is pretty trivial to support - we
just need to check if the request needed to go through poll to complete.

This reuses the IORING_CQE_F_SOCK_NONEMPTY flag value, which is only
valid for recv operations. As IORING_CQE_F_SOCK_FULL only applies on
sends, there's no need for separate values for this flag.

Based on an earlier patchset, which utilized REQ_F_POLL_ARMED instead
and handled patch 1 a bit differently.

 include/linux/io_uring_types.h |  3 +++
 include/uapi/linux/io_uring.h  |  4 ++++
 io_uring/net.c                 | 19 +++++++++++++------
 io_uring/poll.c                |  1 +
 4 files changed, 21 insertions(+), 6 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2025-11-05 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 19:30 Jens Axboe [this message]
2025-11-05 19:30 ` [PATCH 1/2] io_uring/poll: flag request with REQ_F_POLL_TRIGGERED if it went through poll Jens Axboe
2025-11-05 19:30 ` [PATCH 2/2] io_uring/net: add IORING_CQE_F_SOCK_FULL if a send needed to poll arm Jens Axboe
2025-11-06 12:19 ` [PATCHSET 0/2] Add support for IORING_CQE_F_SOCK_FULL Pavel Begunkov
2025-11-06 23:24   ` 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=20251105193639.235441-1-axboe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    /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).