All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Hao Xu <haoxu.linux@gmail.com>, io-uring@vger.kernel.org
Subject: Re: [PATCHSET 0/2] Add support for IORING_RECVSEND_POLL_FIRST
Date: Fri, 29 Apr 2022 12:44:29 -0600	[thread overview]
Message-ID: <065df62a-a4bd-27d7-58eb-437d11995890@kernel.dk> (raw)
In-Reply-To: <cc44706e-a249-86b6-55f5-38683ad110af@gmail.com>

On 4/29/22 12:40 PM, Hao Xu wrote:
> 
> 
> On 4/30/22 02:31, Hao Xu wrote:
>> On 4/27/22 09:54, Jens Axboe wrote:
>>> Hi,
>>>
>>> I had a re-think on the flags2 addition [1] that was posted earlier
>>> today, and I don't really like the fact that flags2 then can't work
>>> with ioprio for read/write etc. We might also want to extend the
>>> ioprio field for other types of IO in the future.
>>>
>>> So rather than do that, do a simpler approach and just add an io_uring
>>> specific flag set for send/recv and friends. This then allow setting
>>> IORING_RECVSEND_POLL_FIRST in sqe->addr2 for those, and if set, io_uring
>>> will arm poll first rather than attempt a send/recv operation.
>>>
>>> [1] https://lore.kernel.org/io-uring/20220426183343.150273-1-axboe@kernel.dk/
>>>
>>
>> Hi Jens,
>> Could we use something like the high bits of sqe->fd to store general flags2
>> since I saw the number of open FDs can be about (1<<20) at most.
> 
> oops, sorry my bad, (1<<20) is just a default value..

Indeed, you can certainly go higher and people do.

-- 
Jens Axboe


  reply	other threads:[~2022-04-29 18:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-27  1:54 [PATCHSET 0/2] Add support for IORING_RECVSEND_POLL_FIRST Jens Axboe
2022-04-27  1:54 ` [PATCH 1/2] io_uring: check IOPOLL/ioprio support upfront Jens Axboe
2022-04-27  1:54 ` [PATCH 2/2] io_uring: add POLL_FIRST support for send/sendmsg and recv/recvmsg Jens Axboe
2022-04-27  3:57 ` [PATCHSET 0/2] Add support for IORING_RECVSEND_POLL_FIRST Hao Xu
2022-04-29 18:31 ` Hao Xu
2022-04-29 18:40   ` Hao Xu
2022-04-29 18:44     ` Jens Axboe [this message]
2022-04-29 18:44   ` 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=065df62a-a4bd-27d7-58eb-437d11995890@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=haoxu.linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.