From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH 1/2] blk-mq: dynamic h/w context count
Date: Fri, 15 Jan 2016 11:22:27 -0700 [thread overview]
Message-ID: <20160115182227.GA7253@localhost.localdomain> (raw)
In-Reply-To: <1450397295-24031-1-git-send-email-keith.busch@intel.com>
On Thu, Dec 17, 2015@05:08:14PM -0700, Keith Busch wrote:
> The hardware's provided queue count may change at runtime with resource
> provisioning. This patch allows a block driver to alter the number of
> h/w queues available when its resource count changes.
>
> The main part is a new blk-mq API to request a new number of h/w queues
> for a given live tag set. The new API freezes all queues using that set,
> then adjusts the allocated count prior to remapping these to CPUs.
>
> The bulk of the rest just shifts where h/w contexts and all their
> artifacts are allocated and freed.
>
> The number of max h/w contexts is capped to the number of possible cpus
> since there is no use for more than that. As such, all pre-allocated
> memory for pointers need to account for the max possible rather than
> the initial number of queues.
>
> A side effect of this is that the blk-mq will proceed successfully as
> long as it can allocate at least one h/w context. Previously it would
> fail request queue initialization if less than the requested number
> was allocated.
>
> Signed-off-by: Keith Busch <keith.busch at intel.com>
> ---
Looks good, works well,
Tested-by: Jon Derrick <jonathan.derrick at intel.com>
prev parent reply other threads:[~2016-01-15 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 0:08 [PATCH 1/2] blk-mq: dynamic h/w context count Keith Busch
2015-12-18 0:08 ` [PATCH 2/2] NVMe: Fix possible queue use after freed Keith Busch
2015-12-24 14:23 ` Christoph Hellwig
2016-02-08 19:28 ` Jon Derrick
2016-02-09 19:39 ` Jens Axboe
2015-12-24 14:22 ` [PATCH 1/2] blk-mq: dynamic h/w context count Christoph Hellwig
2016-01-15 18:22 ` Jon Derrick [this message]
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=20160115182227.GA7253@localhost.localdomain \
--to=jonathan.derrick@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.