From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Bart Van Assche <bvanassche@fusionio.com>,
Robert Elliott <Elliott@hp.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: scsi-mq V2
Date: Wed, 25 Jun 2014 22:50:44 -0600 [thread overview]
Message-ID: <53ABA6A4.8090400@kernel.dk> (raw)
In-Reply-To: <1403715121-1201-1-git-send-email-hch@lst.de>
On 2014-06-25 10:51, Christoph Hellwig wrote:
> This is the second post of the scsi-mq series.
>
> At this point the code is ready for merging and use by developers and early
> adopters. The core blk-mq code isn't that suitable for slow devices
> yet, mostly due to the lack of an I/O scheduler, but Jens is working on it.
> Similarly there is no dm-multipath support for drivers using blk-mq yet,
> but I'm working on it. It should also be noted that the code doesn't
> actually support multiple hardware queues or fine grained tuning of the
> blk-mq parameters yet. All these could be added fairly easily as soon
> as low-level drivers want to make use of them.
>
> The amount of chances to the existing code are fairly small, and mostly
> speedups or cleanups that also apply to the old path as well. Because
> of this I also haven't bothered to put it under a config option, just
> like the blk-mq core.
>
> The usage of blk-mq dramatically decreases CPU usage under all workloads going
> down from 100% CPU usage that the old setup can hit easily to usually less
> than 20% for maxing out storage subsystems with 512byte reads and writes,
> and it allows to easily archive millions of IOPS. Bart and Robert have
> helped with some very detailed measurements that they might be able to send
> in reply to this, although these usually involve significantly reworked low
> level drivers to avoid other bottle necks.
>
> One major objection to previous iterations of this code was the simple
> replacement of the host_lock with atomic counters for the host and busy
> counters. The host_lock avoidance on it's own already improves performance,
> and with the patch to avoid maintaining the per-target busy counter unless
> needed we now replace a lock round trip on the host_lock with just a single
> atomic increment in the submission path, and a single atomic decrement in
> completion path, which should provide benefits even for the oddest RISC
> architecture. Longer term I'd still love to get rid of these entirely
> and use the counters in blk-mq, but due to the difference in how they
> are maintained this doesn't seem feasible as long as we still need to
> support the legacy request code path.
>
> Changes from V1:
> - rebased on top of the core-for-3.17 branch, most notable the
> scsi logging changes
> - fixed handling of cmd_list to prevent crashes for some heavy
> workloads
> - fixed incorrect handling of !target->can_queue
> - avoid scheduling a workqueue on I/O completions when no queues
> are congested
>
> In addition to the patches in this thread there also is a git available at:
>
> git://git.infradead.org/users/hch/scsi.git scsi-mq.2
You can add my acked/reviewed-by to the series.
--
Jens Axboe
next prev parent reply other threads:[~2014-06-26 4:50 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 16:51 scsi-mq V2 Christoph Hellwig
2014-06-25 16:51 ` [PATCH 01/14] sd: don't use rq->cmd_len before setting it up Christoph Hellwig
2014-07-09 11:12 ` Hannes Reinecke
2014-07-09 15:03 ` Christoph Hellwig
2014-06-25 16:51 ` [PATCH 02/14] scsi: split __scsi_queue_insert Christoph Hellwig
2014-07-09 11:12 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 03/14] scsi: centralize command re-queueing in scsi_dispatch_fn Christoph Hellwig
2014-07-08 20:51 ` Elliott, Robert (Server Storage)
2014-07-09 6:40 ` Christoph Hellwig
2014-07-09 11:13 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 04/14] scsi: set ->scsi_done before calling scsi_dispatch_cmd Christoph Hellwig
2014-07-09 11:14 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 05/14] scsi: push host_lock down into scsi_{host,target}_queue_ready Christoph Hellwig
2014-07-09 11:14 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 06/14] scsi: convert target_busy to an atomic_t Christoph Hellwig
2014-07-09 11:15 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 07/14] scsi: convert host_busy to atomic_t Christoph Hellwig
2014-07-09 11:15 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 08/14] scsi: convert device_busy " Christoph Hellwig
2014-07-09 11:16 ` Hannes Reinecke
2014-07-09 16:49 ` James Bottomley
2014-07-10 6:01 ` Christoph Hellwig
2014-06-25 16:51 ` [PATCH 09/14] scsi: fix the {host,target,device}_blocked counter mess Christoph Hellwig
2014-07-09 11:12 ` Hannes Reinecke
2014-07-10 6:06 ` Christoph Hellwig
2014-06-25 16:51 ` [PATCH 10/14] scsi: only maintain target_blocked if the driver has a target queue limit Christoph Hellwig
2014-07-09 11:19 ` Hannes Reinecke
2014-07-09 15:05 ` Christoph Hellwig
2014-06-25 16:51 ` [PATCH 11/14] scsi: unwind blk_end_request_all and blk_end_request_err calls Christoph Hellwig
2014-07-09 11:20 ` Hannes Reinecke
2014-06-25 16:51 ` [PATCH 12/14] scatterlist: allow chaining to preallocated chunks Christoph Hellwig
2014-07-09 11:21 ` Hannes Reinecke
2014-06-25 16:52 ` [PATCH 13/14] scsi: add support for a blk-mq based I/O path Christoph Hellwig
2014-07-09 11:25 ` Hannes Reinecke
2014-07-16 11:13 ` Mike Christie
2014-07-16 11:16 ` Christoph Hellwig
2014-06-25 16:52 ` [PATCH 14/14] fnic: reject device resets without assigned tags for the blk-mq case Christoph Hellwig
2014-07-09 11:27 ` Hannes Reinecke
2014-06-26 4:50 ` Jens Axboe [this message]
2014-06-26 22:07 ` scsi-mq V2 Elliott, Robert (Server Storage)
2014-06-27 14:42 ` Bart Van Assche
2014-06-30 15:20 ` Jens Axboe
2014-06-30 15:25 ` Christoph Hellwig
2014-06-30 15:54 ` Martin K. Petersen
2014-07-08 14:48 ` Christoph Hellwig
2014-07-09 16:39 ` Douglas Gilbert
2014-07-09 19:38 ` Jens Axboe
2014-07-10 0:53 ` Elliott, Robert (Server Storage)
2014-07-10 6:20 ` Christoph Hellwig
2014-07-10 13:36 ` Benjamin LaHaise
2014-07-10 13:39 ` Jens Axboe
2014-07-10 13:44 ` Benjamin LaHaise
2014-07-10 13:48 ` Jens Axboe
2014-07-10 13:50 ` Benjamin LaHaise
2014-07-10 13:52 ` Jens Axboe
2014-07-10 13:50 ` Christoph Hellwig
2014-07-10 13:52 ` Jens Axboe
2014-07-10 14:36 ` Elliott, Robert (Server Storage)
2014-07-10 14:45 ` Benjamin LaHaise
2014-07-10 15:11 ` Jeff Moyer
2014-07-10 19:59 ` Jens Axboe
2014-07-10 20:05 ` Jeff Moyer
2014-07-10 20:06 ` Jens Axboe
2014-07-10 15:51 ` Elliott, Robert (Server Storage)
2014-07-10 16:04 ` Christoph Hellwig
2014-07-10 16:14 ` Christoph Hellwig
2014-07-10 18:49 ` Elliott, Robert (Server Storage)
2014-07-10 19:14 ` Jeff Moyer
2014-07-10 19:36 ` Jeff Moyer
2014-07-10 21:10 ` Elliott, Robert (Server Storage)
2014-07-11 6:02 ` Elliott, Robert (Server Storage)
2014-07-11 6:14 ` Christoph Hellwig
2014-07-11 14:33 ` Elliott, Robert (Server Storage)
2014-07-11 14:55 ` Benjamin LaHaise
2014-07-12 21:50 ` Elliott, Robert (Server Storage)
2014-07-12 23:20 ` Elliott, Robert (Server Storage)
2014-07-13 17:15 ` Elliott, Robert (Server Storage)
2014-07-14 17:15 ` Benjamin LaHaise
2014-07-14 9:13 ` Sagi Grimberg
2014-08-21 12:32 ` Performance degradation in IO writes vs. reads (was scsi-mq V2) Sagi Grimberg
2014-08-21 13:03 ` Christoph Hellwig
2014-08-21 14:02 ` Sagi Grimberg
2014-08-24 16:41 ` Sagi Grimberg
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=53ABA6A4.8090400@kernel.dk \
--to=axboe@kernel.dk \
--cc=Elliott@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@fusionio.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).