From: JeffleXu <[email protected]>
To: Mikulas Patocka <[email protected]>,
Mike Snitzer <[email protected]>,
Heinz Mauelshagen <[email protected]>,
[email protected], [email protected],
[email protected], [email protected],
[email protected], [email protected], [email protected]
Subject: Re: [dm-devel] [PATCH 2/4] block: dont clear REQ_HIPRI for bio-based drivers
Date: Wed, 3 Mar 2021 10:21:23 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 3/3/21 3:05 AM, Mikulas Patocka wrote:
> Don't clear REQ_HIPRI for bio-based drivers. Device mapper will need to
> see this flag in order to support polling.
>
> Signed-off-by: Mikulas Patocka <[email protected]>
>
> ---
> block/blk-core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-2.6/block/blk-core.c
> ===================================================================
> --- linux-2.6.orig/block/blk-core.c 2021-03-02 10:43:28.000000000 +0100
> +++ linux-2.6/block/blk-core.c 2021-03-02 10:53:50.000000000 +0100
I notice that the diff header indicates that the code base is from
linux-2.6. Or it's just the name of your directory, while the code base
is for the latest upstream 5.12?
> @@ -836,7 +836,7 @@ static noinline_for_stack bool submit_bi
> }
> }
>
> - if (!test_bit(QUEUE_FLAG_POLL, &q->queue_flags))
> + if (!test_bit(QUEUE_FLAG_POLL, &q->queue_flags) && !bdev->bd_disk->fops->submit_bio)
> bio->bi_opf &= ~REQ_HIPRI;
>
> switch (bio_op(bio)) {
>
> --
What if dm device is built upon mq devices that are not capable of
polling, i.e., mq devices without QUEUE_FLAG_POLL set? Then this dm
device shall not support polling.
--
Thanks,
Jeffle
next prev parent reply other threads:[~2021-03-03 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 19:05 [PATCH 2/4] block: dont clear REQ_HIPRI for bio-based drivers Mikulas Patocka
2021-03-03 2:21 ` JeffleXu [this message]
2021-03-03 10:05 ` [dm-devel] " Mikulas Patocka
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=3e8b3b2e-f1f4-e946-4858-d2c78e2a8825@linux.alibaba.com \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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