summaryrefslogtreecommitdiffstats
path: root/drivers/block
diff options
context:
space:
mode:
authorJens Axboe <axboe@fb.com>2015-03-06 12:56:13 -0700
committerJens Axboe <axboe@fb.com>2015-03-31 10:41:34 -0600
commitd31af0a325ca4ff8e57b8616ab2228913df369ad (patch)
tree8602f86e0a812a435ce35ef22ed0aadaa88d937f /drivers/block
parentf137e0f15101c0a0ff8a5d956042e50247f1fef9 (diff)
downloadlinux-d31af0a325ca4ff8e57b8616ab2228913df369ad.tar.gz
linux-d31af0a325ca4ff8e57b8616ab2228913df369ad.tar.bz2
linux-d31af0a325ca4ff8e57b8616ab2228913df369ad.zip
NVMe: increase depth of admin queue
Usually the admin queue depth of 64 is plenty, but for some use cases we really need it larger. Examples are use cases like MAT, where you have to touch all of NAND for init/format like purposes. In those cases, we see a good 2x increase with an increased queue depth. Signed-off-by: Jens Axboe <axboe@fb.com> Acked-by: Keith Busch <keith.busch@intel.com>
Diffstat (limited to 'drivers/block')
-rw-r--r--drivers/block/nvme-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 4dc858b43c92..ef432786213b 100644
--- a/drivers/block/nvme-core.c
+++ b/drivers/block/nvme-core.c
@@ -44,7 +44,7 @@
#define NVME_MINORS (1U << MINORBITS)
#define NVME_Q_DEPTH 1024
-#define NVME_AQ_DEPTH 64
+#define NVME_AQ_DEPTH 256
#define SQ_SIZE(depth) (depth * sizeof(struct nvme_command))
#define CQ_SIZE(depth) (depth * sizeof(struct nvme_completion))
#define ADMIN_TIMEOUT (admin_timeout * HZ)