From: Jens Axboe <[email protected]>
To: Hao Xu <[email protected]>
Cc: [email protected], Pavel Begunkov <[email protected]>,
Joseph Qi <[email protected]>
Subject: Re: [PATCH 5.13 v2] io_uring: maintain drain requests' logic
Date: Wed, 7 Apr 2021 09:49:41 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/7/21 5:23 AM, Hao Xu wrote:
> more tests comming, send this out first for comments.
>
> Hao Xu (3):
> io_uring: add IOSQE_MULTI_CQES/REQ_F_MULTI_CQES for multishot requests
> io_uring: maintain drain logic for multishot requests
> io_uring: use REQ_F_MULTI_CQES for multipoll IORING_OP_ADD
>
> fs/io_uring.c | 34 +++++++++++++++++++++++++++++-----
> include/uapi/linux/io_uring.h | 8 +++-----
> 2 files changed, 32 insertions(+), 10 deletions(-)
Let's do the simple cq_extra first. I don't see a huge need to add an
IOSQE flag for this, probably best to just keep this on a per opcode
basis for now, which also then limits the code path to just touching
poll for now, as nothing else supports multishot CQEs at this point.
--
Jens Axboe
next prev parent reply other threads:[~2021-04-07 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 11:23 [PATCH 5.13 v2] io_uring: maintain drain requests' logic Hao Xu
2021-04-07 11:23 ` [PATCH 1/3] io_uring: add IOSQE_MULTI_CQES/REQ_F_MULTI_CQES for multishot requests Hao Xu
2021-04-07 11:38 ` Pavel Begunkov
2021-04-07 11:23 ` [PATCH 2/3] io_uring: maintain drain logic " Hao Xu
2021-04-07 11:41 ` Pavel Begunkov
2021-04-07 11:23 ` [PATCH 3/3] io_uring: use REQ_F_MULTI_CQES for multipoll IORING_OP_ADD Hao Xu
2021-04-07 15:49 ` Jens Axboe [this message]
2021-04-08 10:16 ` [PATCH 5.13 v2] io_uring: maintain drain requests' logic Hao Xu
2021-04-08 11:43 ` Hao Xu
2021-04-08 12:22 ` Pavel Begunkov
2021-04-08 16:18 ` Jens Axboe
2021-04-09 6:15 ` Hao Xu
2021-04-09 7:05 ` Hao Xu
2021-04-09 7:50 ` Pavel Begunkov
2021-04-12 15:07 ` Hao Xu
2021-04-12 15:29 ` Hao Xu
2021-04-09 3:12 ` Hao Xu
2021-04-09 3:43 ` Hao Xu
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] \
[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