From: Pavel Begunkov <asml.silence@gmail.com>
To: Hao Xu <haoxu@linux.alibaba.com>, Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, Joseph Qi <joseph.qi@linux.alibaba.com>
Subject: Re: [PATCH for-5.16 0/2] async hybrid, a new way for pollable requests
Date: Sat, 9 Oct 2021 13:51:00 +0100 [thread overview]
Message-ID: <57f4b76d-6148-98e2-3550-8fde5a4638f7@gmail.com> (raw)
In-Reply-To: <20211008123642.229338-1-haoxu@linux.alibaba.com>
On 10/8/21 13:36, Hao Xu wrote:
> this is a new feature for pollable requests, see detail in commit
> message.
It really sounds we should do it as a part of IOSQE_ASYNC, so
what are the cons and compromises?
> Hao Xu (2):
> io_uring: add IOSQE_ASYNC_HYBRID flag for pollable requests
btw, it doesn't make sense to split it into two patches
> io_uring: implementation of IOSQE_ASYNC_HYBRID logic
>
> fs/io_uring.c | 48 +++++++++++++++++++++++++++++++----
> include/uapi/linux/io_uring.h | 4 ++-
> 2 files changed, 46 insertions(+), 6 deletions(-)
>
--
Pavel Begunkov
next prev parent reply other threads:[~2021-10-09 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 12:36 [PATCH for-5.16 0/2] async hybrid, a new way for pollable requests Hao Xu
2021-10-08 12:36 ` [PATCH 1/2] io_uring: add IOSQE_ASYNC_HYBRID flag " Hao Xu
2021-10-08 12:36 ` [PATCH 2/2] io_uring: implementation of IOSQE_ASYNC_HYBRID logic Hao Xu
2021-10-09 12:46 ` Pavel Begunkov
2021-10-11 8:55 ` Hao Xu
2021-10-11 8:58 ` Hao Xu
2021-10-09 12:51 ` Pavel Begunkov [this message]
2021-10-11 3:08 ` [PATCH for-5.16 0/2] async hybrid, a new way for pollable requests Hao Xu
2021-10-12 11:39 ` Pavel Begunkov
2021-10-14 8:53 ` Hao Xu
2021-10-14 9:20 ` Hao Xu
2021-10-14 13:53 ` Hao Xu
2021-10-14 14:17 ` Pavel Begunkov
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=57f4b76d-6148-98e2-3550-8fde5a4638f7@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=haoxu@linux.alibaba.com \
--cc=io-uring@vger.kernel.org \
--cc=joseph.qi@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).