From: JeffleXu <jefflexu@linux.alibaba.com>
To: Hannes Reinecke <hare@suse.de>, Ming Lei <ming.lei@redhat.com>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com
Subject: Re: [PATCH V4 11/12] block: add poll_capable method to support bio-based IO polling
Date: Tue, 30 Mar 2021 14:50:51 +0800 [thread overview]
Message-ID: <a213b9b1-992d-3deb-200d-c74eac500747@linux.alibaba.com> (raw)
In-Reply-To: <162f000f-7f86-8988-4a15-2c3bf70de1b7@suse.de>
On 3/30/21 2:26 PM, Hannes Reinecke wrote:
> On 3/29/21 5:26 PM, Ming Lei wrote:
>> From: Jeffle Xu <jefflexu@linux.alibaba.com>
>>
>> This method can be used to check if bio-based device supports IO polling
>> or not. For mq devices, checking for hw queue in polling mode is
>> adequate, while the sanity check shall be implementation specific for
>> bio-based devices. For example, dm device needs to check if all
>> underlying devices are capable of IO polling.
>>
>> Though bio-based device may have done the sanity check during the
>> device initialization phase, cacheing the result of this sanity check
>> (such as by cacheing in the queue_flags) may not work. Because for dm
>> devices, users could change the state of the underlying devices through
>> '/sys/block/<dev>/io_poll', bypassing the dm device above. In this case,
>> the cached result of the very beginning sanity check could be
>> out-of-date. Thus the sanity check needs to be done every time 'io_poll'
>> is to be modified.
>>
>> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
>> ---
>> block/blk-sysfs.c | 14 +++++++++++---
>> include/linux/blkdev.h | 1 +
>> 2 files changed, 12 insertions(+), 3 deletions(-)
>>
>> diff --git a/block/blk-sysfs.c b/block/blk-sysfs.c
>> index db3268d41274..c8e7e4af66cb 100644
>> --- a/block/blk-sysfs.c
>> +++ b/block/blk-sysfs.c
>> @@ -426,9 +426,17 @@ static ssize_t queue_poll_store(struct
>> request_queue *q, const char *page,
>> unsigned long poll_on;
>> ssize_t ret;
>> - if (!q->tag_set || q->tag_set->nr_maps <= HCTX_TYPE_POLL ||
>> - !q->tag_set->map[HCTX_TYPE_POLL].nr_queues)
>> - return -EINVAL;
>> + if (queue_is_mq(q)) {
>> + if (!q->tag_set || q->tag_set->nr_maps <= HCTX_TYPE_POLL ||
>> + !q->tag_set->map[HCTX_TYPE_POLL].nr_queues)
>> + return -EINVAL;
>> + } else {
>> + struct gendisk *disk = queue_to_disk(q);
>> +
>> + if (!disk->fops->poll_capable ||
>> + !disk->fops->poll_capable(disk))
>> + return -EINVAL;
>> + }
>> ret = queue_var_store(&poll_on, page, count);
>> if (ret < 0)
>> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
>> index bfab74b45f15..a46f975f2a2f 100644
>> --- a/include/linux/blkdev.h
>> +++ b/include/linux/blkdev.h
>> @@ -1881,6 +1881,7 @@ struct block_device_operations {
>> int (*report_zones)(struct gendisk *, sector_t sector,
>> unsigned int nr_zones, report_zones_cb cb, void *data);
>> char *(*devnode)(struct gendisk *disk, umode_t *mode);
>> + bool (*poll_capable)(struct gendisk *disk);
>> struct module *owner;
>> const struct pr_ops *pr_ops;
>> };
>>
> I really wonder how this would work for nvme multipath; but I guess it
> doesn't change the current situation.
I wonder, at least, md/dm, which is built upon other devices, or
'virtual device' in other words, should be distinguished from other
'original' bio-based device (e.g., nvme multipath) then. Maybe one extra
flag or something.
--
Thanks,
Jeffle
next prev parent reply other threads:[~2021-03-30 6:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 15:26 [PATCH V4 00/12] block: support bio based io polling Ming Lei
2021-03-29 15:26 ` [PATCH V4 01/12] block: add helper of blk_queue_poll Ming Lei
2021-03-29 15:26 ` [PATCH V4 02/12] block: add one helper to free io_context Ming Lei
2021-03-29 15:26 ` [PATCH V4 03/12] block: create io poll context for submission and poll task Ming Lei
2021-03-30 3:54 ` JeffleXu
2021-03-30 6:17 ` Hannes Reinecke
2021-03-29 15:26 ` [PATCH V4 04/12] block: add req flag of REQ_POLL_CTX Ming Lei
2021-03-30 6:19 ` Hannes Reinecke
2021-03-29 15:26 ` [PATCH V4 05/12] block: add new field into 'struct bvec_iter' Ming Lei
2021-03-29 15:26 ` [PATCH V4 06/12] block/mq: extract one helper function polling hw queue Ming Lei
2021-03-29 15:26 ` [PATCH V4 07/12] block: prepare for supporting bio_list via other link Ming Lei
2021-03-29 15:26 ` [PATCH V4 08/12] block: use per-task poll context to implement bio based io polling Ming Lei
2021-03-30 3:52 ` JeffleXu
2021-03-30 6:40 ` Hannes Reinecke
2021-03-30 8:32 ` Ming Lei
2021-03-29 15:26 ` [PATCH V4 09/12] blk-mq: limit hw queues to be polled in each blk_poll() Ming Lei
2021-03-30 3:53 ` JeffleXu
2021-03-29 15:26 ` [PATCH V4 10/12] block: add queue_to_disk() to get gendisk from request_queue Ming Lei
2021-03-30 6:27 ` Hannes Reinecke
2021-03-29 15:26 ` [PATCH V4 11/12] block: add poll_capable method to support bio-based IO polling Ming Lei
2021-03-30 6:26 ` Hannes Reinecke
2021-03-30 6:50 ` JeffleXu [this message]
2021-03-30 8:49 ` Ming Lei
2021-03-29 15:26 ` [PATCH V4 12/12] dm: support IO polling for bio-based dm device Ming Lei
2021-03-30 6:40 ` Hannes Reinecke
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=a213b9b1-992d-3deb-200d-c74eac500747@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=snitzer@redhat.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