[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1401742510-10827-1-git-send-email-m@bjorling.me>
Date: Mon, 2 Jun 2014 22:55:09 +0200
From: Matias Bjørling <m@...rling.me>
To: willy@...ux.intel.com, keith.busch@...el.com, sbradshaw@...ron.com,
axboe@...nel.dk, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, hch@...radead.org
Cc: Matias Bjørling <m@...rling.me>
Subject: [PATCH v5] conversion to blk-mq
Hi Matthew and Keith,
Here is an updated patch with the feedback from the previous days. It's against
Jens' for-3.16/core tree. You may use the nvmemq_wip_review branch at:
https://github.com/MatiasBjorling/linux-collab nvmemq_wip_review
and see the changes from v4 to v5 here:
https://github.com/MatiasBjorling/linux-collab/commit/e650bc5
Changes since v4:
* Fix timeout retries
* Fix naming in nvme_init_hctx
* Fix racy behavior of admin queue in nvme_dev_remove
* Fix wrong return values in nvme_queue_request
* Put cqe_seen back
* Introduce abort_completion for killing timed out I/Os
* Move locks outside of nvme_submit_iod
* Various renaming and style fixes
Changes since v3:
* Added abortion logic
* Fixed possible race on abortion
* Removed req data with flush. Handled by by blk-mq
* Added safety check for submitting user rq to admin queue.
* Use dev->online_queues for nr_hw_queues
* Fix loop with initialization in nvme_create_io_queues
* Style fixups
Changes since v2:
* rebased on top of current 3.16/core.
* use blk-mq queue management for spreading io queues
* removed rcu handling and allocated all io queues up front for mgmt by blk-mq
* removed the need for hotplugging notification
* fixed flush data handling
* fixed double free of spinlock
* various cleanup
Matias Bjørling (1):
NVMe: conversion to blk-mq
drivers/block/nvme-core.c | 1149 ++++++++++++++++++---------------------------
drivers/block/nvme-scsi.c | 8 +-
include/linux/nvme.h | 14 +-
3 files changed, 478 insertions(+), 693 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists