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: Thu, 04 Oct 2018 13:09:06 -0700 Message-ID: <1538683746.230807.9.camel@acm.org> References: <20181002124329.21248-1-linus.walleij@linaro.org> <05fdbe23-ec01-895f-e67e-abff85c1ece2@kernel.dk> <1538582091.205649.20.camel@acm.org> <20181004202553.71c2599c@alans-desktop> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-7" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20181004202553.71c2599c@alans-desktop> Sender: linux-kernel-owner@vger.kernel.org To: Alan Cox Cc: Paolo Valente , Jens Axboe , Linus Walleij , linux-block , linux-mmc , linux-mtd@lists.infradead.org, Pavel Machek , Ulf Hansson , Richard Weinberger , Artem Bityutskiy , Adrian Hunter , Jan Kara , Andreas Herrmann , Mel Gorman , Chunyan Zhang , linux-kernel List-Id: linux-mmc@vger.kernel.org On Thu, 2018-10-04 at 20:25 +-0100, Alan Cox wrote: +AD4 +AD4 I agree with Jens that it's best to leave it to the Linux distributors to +AD4 +AD4 select a default I/O scheduler. +AD4 +AD4 That assumes such a thing exists. The kernel knows what devices it is +AD4 dealing with. The kernel 'default' ought to be 'whatever is usually best +AD4 for this device'. A distro cannot just pick a correct single default +AD4 because NVME and USB sticks are both normal and rather different in needs. Which I/O scheduler works best also depends which workload the user will run. BFQ has significant advantages for interactive workloads like video replay with concurrent background I/O but probably slows down kernel builds. That's why I'm not sure whether the kernel should select the default I/O scheduler. Bart.