From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 0/3] Add BLK_MQ_F_NO_SCHED flag to admin tag set
Date: Wed, 18 Oct 2017 17:31:56 +0300 [thread overview]
Message-ID: <7c0b3811-6df7-3bb7-b527-3995fdaeccb6@grimberg.me> (raw)
In-Reply-To: <4f73e090-513c-aa07-a4aa-fcea4bc944a0@mellanox.com>
>>> Since commit b86dd81
>>> "block: get rid of blk-mq default scheduler choice Kconfig entries",
>>> when setting nr_hw_queues to 1 the admin tag set uses mq-deadline
>>> scheduler.
>>> This flag is useful for admin queues that aren't used for normal IO.
>>> We already use this flag at nvme-pci.
>>
>> How is the fact that we set a single hw queue has anything to do with
>> the admin tagset?
>
> Setting nr_hw_queues attribute of admin tag set to 1 influence the value
> of nr_hw_queues attribute of the admin queue.
> At /block/elevator.c
> elevator_init() selects the scheduler according to the value of
> nr_hw_queues
> attribute of the admin queue.
Oh, I confused your meaning with setting nr_hw_queues to 1 in the IO
tagset makes a difference for the admin tagset.
next prev parent reply other threads:[~2017-10-18 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 12:38 [PATCH 0/3] Add BLK_MQ_F_NO_SCHED flag to admin tag set Israel Rukshin
2017-10-18 12:38 ` [PATCH 1/3] nvme-rdma: " Israel Rukshin
2017-10-18 15:30 ` Sagi Grimberg
2017-10-18 12:38 ` [PATCH 2/3] nvme-fc: " Israel Rukshin
2017-10-18 15:30 ` Sagi Grimberg
2017-10-18 21:41 ` James Smart
2017-10-18 12:38 ` [PATCH 3/3] nvme-loop: " Israel Rukshin
2017-10-18 15:30 ` Sagi Grimberg
2017-10-18 12:50 ` [PATCH 0/3] " Sagi Grimberg
2017-10-18 13:58 ` Israel Rukshin
2017-10-18 14:31 ` Sagi Grimberg [this message]
2017-10-18 15:16 ` Israel Rukshin
2017-10-18 20:05 ` [Suspected-Phishing][PATCH " Max Gurtovoy
2017-10-19 8:59 ` [PATCH " Christoph Hellwig
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=7c0b3811-6df7-3bb7-b527-3995fdaeccb6@grimberg.me \
--to=sagi@grimberg.me \
/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).