From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [GIT PULL] block IO core bits for 3.13
Date: Thu, 14 Nov 2013 00:16:00 -0800 [thread overview]
Message-ID: <1384416960.18704.47.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <20131108174856.GA3195@kernel.dk>
On Fri, 2013-11-08 at 10:48 -0700, Jens Axboe wrote:
> Hi Linus,
>
> This is the pull request for the core changes in the block layer for
> 3.13. It contains:
>
> - The new blk-mq request interface. This is a new and more scalable
> queueing model that marries the best part of the request based
> interface we currently have (which is fully featured, but scales
> poorly) and the bio based "interface" which the new drivers for high
> IOPS devices end up using because it's much faster than the request
> based one. The bio interface has no block layer support, since it taps
> into the stack much earlier. This means that drivers end up having to
> implement a lot of functionality on their own, like tagging, timeout
> handling, requeue, etc. The blk-mq interface provides all these. Some
> drivers even provide a switch to select bio or rq and has code to
> handle both, since things like merging only works in the rq model and
> hence is faster for some workloads. This is a huge mess. Conversion of
> these drivers nets us a substantial code reduction. Initial results on
> converting SCSI to this model even shows an 8x improvement on single
> queue devices. So while the model was intended to work on the newer
> multiqueue devices, it has substantial improvements for "classic"
> hardware as well. This code has gone through extensive testing and
> development, it's now ready to go. A pull request is coming to convert
> virtio-blk to this model will be will be coming as well, with more
> drivers scheduled for 3.14 conversion.
>
Hey Jens,
Just wanted to say, congratulations on this evenings merge of blk-mq!
I'm really excited to see this code upstream in v3.13, and the merge
being a catalyst for the next generation of flash device design that
takes advantage of all blk-mq has to offer.
Not to mention, progressing scsi-mq forward from alpha prototype -> beta
status over the next months, to move beyond our current SCSI initiator
performance constraints.
So, perhaps fitting NAME for v3.13 would be along the lines of
"I/O, the next generation".
;-)
--nab
prev parent reply other threads:[~2013-11-14 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 17:48 Jens Axboe
2013-11-14 8:16 ` Nicholas A. Bellinger [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=1384416960.18704.47.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®