From: Pavel Begunkov <[email protected]>
To: Avi Kivity <[email protected]>, Jens Axboe <[email protected]>,
[email protected]
Subject: Re: IORING_OP_POLL_ADD slower than linux-aio IOCB_CMD_POLL
Date: Wed, 15 Jun 2022 12:38:39 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/15/22 12:07, Avi Kivity wrote:
> Sorry, hit send too quiclky.
>>>> If this is correct (it's not unreasonable, but should be documented), then there should also be a simple way to force a kernel entry. But how to do this using liburing? IIUC if I the following apply:
>>>>
>>>>
>>>> 1. I have no pending sqes
>>>>
>>>> 2. There are pending completions
>>>>
>>>> 3. There is a completed event for which a completion has not been appended to the completion queue ring
>>>>
>>>>
>>>> Then io_uring_wait_cqe() will elide io_uring_enter() and the completed-but-not-reported event will be delayed.
>>>
>>> One way is to process all CQEs and then it'll try to enter the
>>> kernel and do the job.
>
>
> But I don't want it to wait. I want it to generate pending completions, and return immediately even if no completions were generated. I have some background computations I'm happy to perform if no events are pending, but I would like those events to be generated promptly.
Ok, then you may want IORING_SETUP_TASKRUN_FLAG described below.
btw IORING_SETUP_TASKRUN_FLAG has some additional overhead.
>>> Another way is to also set IORING_SETUP_TASKRUN_FLAG, then when
>>> there is work that requires to enter the kernel io_uring will
>>> set IORING_SQ_TASKRUN in sq_flags.
>>> Actually, I'm not mistaken io_uring has some automagic handling
>>> of it internally
>>>
>>> https://github.com/axboe/liburing/blob/master/src/queue.c#L36
>>>
>
> Is there documentation about this flag?
Unfortunately, I don't see any.
Here is a link to the kernel commit if it helps:
https://git.kernel.dk/cgit/linux-block/commit/?h=ef060ea9e4fd3b763e7060a3af0a258d2d5d7c0d
I think it's more interesting what support liburing has,
but would need to look up in the code. Maybe Jens
remembers and can tell.
--
Pavel Begunkov
next prev parent reply other threads:[~2022-06-15 11:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 11:07 IORING_OP_POLL_ADD slower than linux-aio IOCB_CMD_POLL Avi Kivity
2022-04-19 11:38 ` Jens Axboe
2022-04-19 11:57 ` Avi Kivity
2022-04-19 12:04 ` Jens Axboe
2022-04-19 12:21 ` Avi Kivity
2022-04-19 12:31 ` Jens Axboe
2022-04-19 15:21 ` Jens Axboe
2022-04-19 15:51 ` Avi Kivity
2022-04-19 17:14 ` Jens Axboe
2022-04-19 19:41 ` Avi Kivity
2022-04-19 19:58 ` Jens Axboe
2022-04-20 11:55 ` Avi Kivity
2022-04-20 12:09 ` Jens Axboe
2022-04-21 9:05 ` Avi Kivity
2022-06-15 10:12 ` Avi Kivity
2022-06-15 10:48 ` Pavel Begunkov
2022-06-15 11:04 ` Avi Kivity
2022-06-15 11:07 ` Avi Kivity
2022-06-15 11:38 ` Pavel Begunkov [this message]
2022-06-15 12:21 ` Jens Axboe
2022-06-15 13:43 ` Avi Kivity
2022-06-15 11:30 ` Pavel Begunkov
2022-06-15 11:36 ` Avi Kivity
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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