From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Pavel Machek <pavel@ucw.cz>, Ulf Hansson <ulf.hansson@linaro.org>,
Richard Weinberger <richard@nod.at>,
Adrian Hunter <adrian.hunter@intel.com>, Jan Kara <jack@suse.cz>,
"aherrmann@suse.com" <aherrmann@suse.com>,
"mgorman@suse.com" <mgorman@suse.com>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bfq-iosched@googlegroups.com" <bfq-iosched@googlegroups.com>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] block: BFQ default for single queue devices
Date: Wed, 3 Oct 2018 05:51:46 -0700 [thread overview]
Message-ID: <20181003125146.GA9313@infradead.org> (raw)
In-Reply-To: <BN3PR0401MB164003C967C45F2681F503A7E7E90@BN3PR0401MB1640.namprd04.prod.outlook.com>
On Wed, Oct 03, 2018 at 07:42:15AM +0000, Damien Le Moal wrote:
> Of note also is that host-managed like sequential zone devices are also likely
> to show up soon with the work being done in the NVMe standard on the new "Zoned
> namespace" feature proposal. These devices will also require a scheduler like
> mq-deadline guaranteeing per-zone in-order delivery of sequential write
> requests. Looking only at the number of queues of the device is not enough to
> choose the best (most reasonnable/appropriate) scheduler.
We actually have a plan to avoid the need for a non-reordering scheduler
there (including a Linux prototype for it). Lets see if it survives the
committee.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <Damien.LeMoal@wdc.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Pavel Machek <pavel@ucw.cz>, Ulf Hansson <ulf.hansson@linaro.org>,
Richard Weinberger <richard@nod.at>,
Adrian Hunter <adrian.hunter@intel.com>, Jan Kara <jack@suse.cz>,
"aherrmann@suse.com" <aherrmann@suse.com>,
"mgorman@suse.com" <mgorman@suse.com>,
Chunyan Zhang <zhang.chunyan@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bfq-iosched@googlegroups.com" <bfq-iosched@googlegroups.com>,
"oleksandr@natalenko.name" <oleksandr@n>
Subject: Re: [PATCH] block: BFQ default for single queue devices
Date: Wed, 3 Oct 2018 05:51:46 -0700 [thread overview]
Message-ID: <20181003125146.GA9313@infradead.org> (raw)
In-Reply-To: <BN3PR0401MB164003C967C45F2681F503A7E7E90@BN3PR0401MB1640.namprd04.prod.outlook.com>
On Wed, Oct 03, 2018 at 07:42:15AM +0000, Damien Le Moal wrote:
> Of note also is that host-managed like sequential zone devices are also likely
> to show up soon with the work being done in the NVMe standard on the new "Zoned
> namespace" feature proposal. These devices will also require a scheduler like
> mq-deadline guaranteeing per-zone in-order delivery of sequential write
> requests. Looking only at the number of queues of the device is not enough to
> choose the best (most reasonnable/appropriate) scheduler.
We actually have a plan to avoid the need for a non-reordering scheduler
there (including a Linux prototype for it). Lets see if it survives the
committee.
next prev parent reply other threads:[~2018-10-03 12:51 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 12:43 [PATCH] block: BFQ default for single queue devices Linus Walleij
2018-10-02 12:43 ` Linus Walleij
2018-10-02 14:31 ` Jens Axboe
2018-10-02 14:31 ` Jens Axboe
2018-10-02 14:45 ` Linus Walleij
2018-10-02 14:45 ` Linus Walleij
2018-10-03 6:29 ` Paolo Valente
2018-10-03 6:29 ` Paolo Valente
2018-10-03 6:53 ` Linus Walleij
2018-10-03 13:25 ` Jan Kara
2018-10-04 7:45 ` Johannes Thumshirn
2018-10-04 7:45 ` Johannes Thumshirn
2018-10-04 8:24 ` Andreas Herrmann
2018-10-03 7:05 ` Artem Bityutskiy
2018-10-03 7:18 ` Linus Walleij
2018-10-03 7:42 ` Damien Le Moal
2018-10-03 7:42 ` Damien Le Moal
2018-10-03 8:28 ` Linus Walleij
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 8:53 ` Damien Le Moal
2018-10-03 15:53 ` Paolo Valente
2018-10-03 15:53 ` Paolo Valente
2018-10-03 17:34 ` Bryan Gurney
2018-10-04 8:21 ` Linus Walleij
2018-10-04 9:56 ` Ulf Hansson
2018-10-03 12:51 ` Christoph Hellwig [this message]
2018-10-03 12:51 ` Christoph Hellwig
2018-10-03 14:58 ` Bart Van Assche
2018-10-03 14:58 ` Bart Van Assche
2018-10-03 15:01 ` Christoph Hellwig
2018-10-03 15:01 ` Christoph Hellwig
2018-10-03 15:15 ` Bart Van Assche
2018-10-03 15:15 ` Bart Van Assche
2018-10-05 6:24 ` Christoph Hellwig
2018-10-05 6:24 ` Christoph Hellwig
2018-10-03 15:52 ` Paolo Valente
2018-10-03 15:52 ` Paolo Valente
2018-10-03 15:52 ` Paolo Valente
2018-10-03 11:49 ` Oleksandr Natalenko
2018-10-03 11:49 ` Oleksandr Natalenko
2018-10-03 14:51 ` Mark Brown
2018-10-03 15:55 ` Paolo Valente
2018-10-03 15:55 ` Paolo Valente
2018-10-03 16:00 ` Bart Van Assche
2018-10-03 16:04 ` Paolo Valente
2018-10-03 16:04 ` Paolo Valente
2018-10-04 7:38 ` Jan Kara
2018-10-04 8:14 ` Linus Walleij
2018-10-04 10:13 ` Mark Brown
2018-10-04 15:10 ` Bart Van Assche
2018-10-04 15:26 ` Mark Brown
2018-10-05 9:49 ` Pavel Machek
2018-10-04 8:25 ` Linus Walleij
2018-10-03 15:54 ` Bart Van Assche
2018-10-03 15:54 ` Bart Van Assche
2018-10-03 16:02 ` Paolo Valente
2018-10-03 16:02 ` Paolo Valente
2018-10-03 16:09 ` Paolo Valente
2018-10-03 17:22 ` Paolo Valente
2018-10-03 17:22 ` Paolo Valente
2018-10-04 19:25 ` Alan Cox
2018-10-04 19:25 ` Alan Cox
2018-10-04 20:09 ` Bart Van Assche
2018-10-04 20:39 ` Paolo Valente
2018-10-04 20:39 ` Paolo Valente
2018-10-04 22:42 ` Bart Van Assche
2018-10-05 9:16 ` Jan Kara
2018-10-06 3:12 ` Bart Van Assche
2018-10-06 6:46 ` Paolo Valente
2018-10-06 6:46 ` Paolo Valente
2018-10-06 6:46 ` Paolo Valente
2018-10-06 16:20 ` Bart Van Assche
2018-10-06 16:20 ` Bart Van Assche
2018-10-06 16:46 ` Paolo Valente
2018-10-06 16:46 ` Paolo Valente
2018-10-06 16:46 ` Paolo Valente
2018-10-05 9:28 ` Paolo Valente
2018-10-05 9:28 ` Paolo Valente
2018-10-05 6:24 ` Artem Bityutskiy
2018-10-04 20:19 ` Paolo Valente
2018-10-04 20:19 ` Paolo Valente
2018-10-02 21:28 ` Richard Weinberger
2018-10-02 21:28 ` Richard Weinberger
2018-10-03 15:51 ` Paolo Valente
2018-10-03 15:51 ` Paolo Valente
2018-10-03 15:51 ` Paolo Valente
2018-10-05 8:04 ` Pavel Machek
2018-10-05 8:04 ` Pavel Machek
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=20181003125146.GA9313@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=adrian.hunter@intel.com \
--cc=aherrmann@suse.com \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=broonie@kernel.org \
--cc=dedekind1@gmail.com \
--cc=jack@suse.cz \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mgorman@suse.com \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=pavel@ucw.cz \
--cc=richard@nod.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.