From: Jens Axboe <axboe@kernel.dk>
To: "Stefan Bühler" <source@stbuehler.de>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1 1/1] [io_uring] require RWF_HIPRI for iopoll reads and writes
Date: Wed, 1 May 2019 06:43:18 -0600 [thread overview]
Message-ID: <628e59c6-716f-5af3-c1dc-bf5cb9003105@kernel.dk> (raw)
In-Reply-To: <20190501115223.13296-1-source@stbuehler.de>
On 5/1/19 5:52 AM, Stefan Bühler wrote:
> This makes the mapping RWF_HIPRI <-> IOCB_HIPRI <-> iopoll more
> consistent; it also allows supporting iopoll operations without
> IORING_SETUP_IOPOLL in the future.
I don't want to make this change now. Additionally, it's never
going to be possible to support polled IO mixed with non-polled
IO on an io_uring instance, as that makes the wait part of IO
impossible to support without adding tracking of requests.
As we can never mix them, it doesn't make a lot of sense to
request RWF_HIPRI for polled IO.
--
Jens Axboe
next prev parent reply other threads:[~2019-05-01 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 11:52 [PATCH v1 1/1] [io_uring] require RWF_HIPRI for iopoll reads and writes Stefan Bühler
2019-05-01 12:43 ` Jens Axboe [this message]
2019-05-01 13:40 ` Stefan Bühler
2019-05-01 14:12 ` 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=628e59c6-716f-5af3-c1dc-bf5cb9003105@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=source@stbuehler.de \
/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).