From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "hare@suse.de" <hare@suse.de>, "arnd@arndb.de" <arnd@arndb.de>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"baolin.wang@linaro.org" <baolin.wang@linaro.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"riteshh@codeaurora.org" <riteshh@codeaurora.org>,
"paolo.valente@linaro.org" <paolo.valente@linaro.org>,
"hch@lst.de" <hch@lst.de>, "axboe@kernel.dk" <axboe@kernel.dk>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"zhang.chunyan@linaro.org" <zhang.chunyan@linaro.org>
Subject: Re: [PATCH v2] RFD: switch MMC/SD to use blk-mq multiqueueing
Date: Mon, 2 Jan 2017 11:58:35 +0000 [thread overview]
Message-ID: <1483358298.3592.52.camel@sandisk.com> (raw)
In-Reply-To: <68863f25-7faa-88b5-78bb-21027f772ab6@suse.de>
On Mon, 2017-01-02 at 12:06 +0100, Hannes Reinecke wrote:
> Hmm. But that would amount to implement yet another queuing mechanism
> within the driver/mmc subsystem, wouldn't it?
>
> Which is, incidentally, the same method the S/390 DASD driver uses
> nowadays; report an arbitrary queue depth to the block layer and queue
> all requests internally to better saturate the device.
>
> However I'd really like to get rid of this, and tweak the block layer to
> handle these cases.
Hello Hannes,
Such functionality will be added to the blk-mq core as part of the
initiative to add blk-mq I/O scheduling support. One implementation has been
proposed by Jens (http://git.kernel.dk/cgit/linux-block/log/?h=blk-mq-sched)
and another implementation has been proposed by myself (https://lkml.org/lkm
l/2016/12/22/322).
Bart.
next prev parent reply other threads:[~2017-01-02 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 14:01 [PATCH v2] RFD: switch MMC/SD to use blk-mq multiqueueing Linus Walleij
2016-12-20 16:21 ` Bartlomiej Zolnierkiewicz
2016-12-21 17:22 ` Ritesh Harjani
2016-12-27 12:21 ` Linus Walleij
2016-12-28 4:21 ` Ritesh Harjani
2016-12-28 8:55 ` Christoph Hellwig
2016-12-28 23:59 ` Linus Walleij
2017-01-02 9:40 ` Arnd Bergmann
2017-01-02 11:06 ` Hannes Reinecke
2017-01-02 11:58 ` Bart Van Assche [this message]
2017-01-02 17:08 ` Arnd Bergmann
2017-01-03 7:50 ` Paolo Valente
2017-01-03 23:06 ` Arnd Bergmann
2017-01-03 12:57 ` Linus Walleij
2017-01-02 11:55 ` Bart Van Assche
2017-01-03 12:59 ` Linus Walleij
2017-01-02 13:56 ` Adrian Hunter
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=1483358298.3592.52.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=baolin.wang@linaro.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=paolo.valente@linaro.org \
--cc=riteshh@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=zhang.chunyan@linaro.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