From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] nvme-pci: only set nr_maps to 2 if poll queues are supported
Date: Fri, 14 Dec 2018 11:50:25 -0700 [thread overview]
Message-ID: <e6ff4bc1-2fbe-9aef-a384-ee19b4788460@kernel.dk> (raw)
In-Reply-To: <9d2fa9e4-927e-655b-5db3-32d8f0a17db7@grimberg.me>
On 12/14/18 11:43 AM, Sagi Grimberg wrote:
>
>> The block layer now enables polling support on a queue if nr_maps
>> includes the poll map, so we should only set that if we actually
>> support poll queues.
>>
>> Fixes: 6544d229bf ("block: enable polling by default if a poll map is initalized")
>
> What does it fix? is there a bug when setting 3 queue maps?
After the recent changes, blk_mq_init_allocated_queue() does this:
if (set->nr_maps > HCTX_TYPE_POLL)
blk_queue_flag_set(QUEUE_FLAG_POLL, q);
since the core doesn't have any notion of how many queues are used for
what. We only support polling if you have explicit poll queues now,
hence the above is wrong if nvme says nr_maps is 3 and it doesn't have
any poll queues.
--
Jens Axboe
next prev parent reply other threads:[~2018-12-14 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 16:20 [PATCH] nvme-pci: only set nr_maps to 2 if poll queues are supported Christoph Hellwig
2018-12-14 16:47 ` Jens Axboe
2018-12-14 16:49 ` Christoph Hellwig
2018-12-14 16:49 ` Jens Axboe
2018-12-14 18:43 ` Sagi Grimberg
2018-12-14 18:50 ` Jens Axboe [this message]
2018-12-14 19:01 ` Sagi Grimberg
2018-12-14 19:36 ` Jens Axboe
2018-12-14 19:49 ` Sagi Grimberg
2018-12-15 1:14 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2018-12-14 15:42 Christoph Hellwig
2018-12-14 15:45 ` 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=e6ff4bc1-2fbe-9aef-a384-ee19b4788460@kernel.dk \
--to=axboe@kernel.dk \
/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