From: jonathan.derrick@intel.com (Jon Derrick)
Subject: [PATCH] nvme: Allow controllers to specify a min queue depth for CMB
Date: Fri, 11 Dec 2015 13:25:46 -0700 [thread overview]
Message-ID: <20151211202546.GA4116@localhost.localdomain> (raw)
In-Reply-To: <20151211200653.GA26595@lst.de>
Hi Christoph,
> - please don't overload the quirks bitmap with actual values
I agree it may not have been the best place for it, but I wasn't sure how/where it could go to be matched with specific devices. Certain devices may want 8, 16, or 32.
> - why do we even need to set a size instead of using up the CMB
> size?
Consider a device with 32kB allocated for CMB. The SQes alignment restriction (detailed below) requires us to align to the controller page size. If we consider an example of 4kB pages, that gives us 8 SQes in the CMB, each with 64 entries (assuming 64B-sized sq entries).
Or instead, we could have 32 queues, each with 1K alignment, and 16 entries (assuming the device is fast enough).
> - why do we even need to add a quirk? I quick look at the spec
> doesn't seem to require us to align the submission queue size
> - this patchs adds a quirk, but no use of it so it's effectively just dead
> code
It is not that apparent. It inherits the restriction on the Create I/O Submission Queue command (NVM-Express 1.2a, 5.4, Figure 54).
next prev parent reply other threads:[~2015-12-11 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 19:36 [PATCH] nvme: Allow controllers to specify a min queue depth for CMB Jon Derrick
2015-12-11 20:06 ` Christoph Hellwig
2015-12-11 20:25 ` Jon Derrick [this message]
2015-12-11 20:33 ` Keith Busch
2015-12-11 20:59 ` Jon Derrick
2015-12-14 10:18 ` 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=20151211202546.GA4116@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.