From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bart Van Assche Subject: Re: [PATCH] block: BFQ default for single queue devices Date: Wed, 03 Oct 2018 07:58:52 -0700 Message-ID: <1538578732.205649.0.camel@acm.org> References: <20181002124329.21248-1-linus.walleij@linaro.org> <05fdbe23-ec01-895f-e67e-abff85c1ece2@kernel.dk> <1538550325.14984.108.camel@gmail.com> <20181003125146.GA9313@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-7" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181003125146.GA9313@infradead.org> Sender: linux-kernel-owner@vger.kernel.org To: Christoph Hellwig , Damien Le Moal Cc: Linus Walleij , Artem Bityutskiy , Paolo Valente , Jens Axboe , linux-block , linux-mmc , "linux-mtd@lists.infradead.org" , Pavel Machek , Ulf Hansson , Richard Weinberger , Adrian Hunter , Jan Kara , "aherrmann@suse.com" , "mgorman@suse.com" , Chunyan Zhang , "linux-kernel@vger.kernel.org" , "bfq-iosched@googlegroups.com" , "oleksandr@natalenko.name" List-Id: linux-mmc@vger.kernel.org On Wed, 2018-10-03 at 05:51 -0700, Christoph Hellwig wrote: +AD4 On Wed, Oct 03, 2018 at 07:42:15AM +-0000, Damien Le Moal wrote: +AD4 +AD4 Of note also is that host-managed like sequential zone devices are also likely +AD4 +AD4 to show up soon with the work being done in the NVMe standard on the new +ACI-Zoned +AD4 +AD4 namespace+ACI feature proposal. These devices will also require a scheduler like +AD4 +AD4 mq-deadline guaranteeing per-zone in-order delivery of sequential write +AD4 +AD4 requests. Looking only at the number of queues of the device is not enough to +AD4 +AD4 choose the best (most reasonnable/appropriate) scheduler. +AD4 +AD4 We actually have a plan to avoid the need for a non-reordering scheduler +AD4 there (including a Linux prototype for it). Lets see if it survives the +AD4 committee. Has the work with the T10 committee to standardize the SCSI equivalent of anonymous writes already started? Thanks, Bart.