public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCHSET 0/2] Add support for IORING_CQE_F_SOCK_FULL
Date: Thu, 6 Nov 2025 16:24:24 -0700	[thread overview]
Message-ID: <991b21db-22d1-4cc2-84cc-19a6a2c94123@kernel.dk> (raw)
In-Reply-To: <c5390f95-22f6-4b21-b1b1-bad44d5fc1e5@gmail.com>

On 11/6/25 5:19 AM, Pavel Begunkov wrote:
> On 11/5/25 19:30, Jens Axboe wrote:
>> 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.
> 
> FWIW, same comments as last time. REQ_F_POLL_TRIGGERED is set not
> in the right place. And, with how tcp manages wait queues, you won't
> be able to use it well for any throttling, as the user will get the
> flagged CQE long time after, when the queue is already half empty.

I'll take a closer look when I'm back, on the road until Monday...

-- 
Jens Axboe


      reply	other threads:[~2025-11-06 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 19:30 [PATCHSET 0/2] Add support for IORING_CQE_F_SOCK_FULL Jens Axboe
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 [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=991b21db-22d1-4cc2-84cc-19a6a2c94123@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --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