From: Jens Axboe <axboe@kernel.dk>
To: Hao Xu <haoxu.linux@gmail.com>, io-uring@vger.kernel.org
Cc: Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH 3/4] io_uring: let fast poll support multishot
Date: Mon, 9 May 2022 21:20:33 -0600 [thread overview]
Message-ID: <ebcb3dc9-4241-0cc9-e24e-677ae8db71a7@kernel.dk> (raw)
In-Reply-To: <SG2PR01MB24118EC72D64732E308F6061FFC79@SG2PR01MB2411.apcprd01.prod.exchangelabs.com>
On 5/8/22 9:32 AM, Hao Xu wrote:
> From: Hao Xu <howeyxu@tencent.com>
>
> For operations like accept, multishot is a useful feature, since we can
> reduce a number of accept sqe. Let's integrate it to fast poll, it may
> be good for other operations in the future.
This, and 1-2 look good to me now.
--
Jens Axboe
next prev parent reply other threads:[~2022-05-10 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220508153203.5544-1-haoxu.linux@gmail.com>
2022-05-08 15:32 ` [PATCH 1/4] io_uring: add IORING_ACCEPT_MULTISHOT for accept Hao Xu
2022-05-08 15:32 ` [PATCH 2/4] io_uring: add REQ_F_APOLL_MULTISHOT for requests Hao Xu
2022-05-08 15:32 ` [PATCH 3/4] io_uring: let fast poll support multishot Hao Xu
2022-05-10 3:20 ` Jens Axboe [this message]
2022-05-08 15:32 ` [PATCH 4/4] io_uring: implement multishot mode for accept Hao Xu
2022-05-10 3:20 ` Jens Axboe
2022-05-14 14:20 [PATCH v6 0/4] fast poll multishot mode Hao Xu
2022-05-14 14:20 ` [PATCH 3/4] io_uring: let fast poll support multishot Hao Xu
[not found] <20220508153747.6184-1-haoxu.linux@gmail.com>
2022-05-08 15:37 ` Hao Xu
[not found] <20220507171504.151739-1-haoxu_linux@126.com>
2022-05-07 17:15 ` Hao Xu
-- strict thread matches above, loose matches on Subject: below --
2022-05-07 14:06 [PATCH v3 0/4] fast poll multishot mode Hao Xu
2022-05-07 14:06 ` [PATCH 3/4] io_uring: let fast poll support multishot 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 \
--in-reply-to=ebcb3dc9-4241-0cc9-e24e-677ae8db71a7@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--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.