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 09:00:46 -0700 Message-ID: <1538582446.205649.22.camel@acm.org> References: <20181002124329.21248-1-linus.walleij@linaro.org> <05fdbe23-ec01-895f-e67e-abff85c1ece2@kernel.dk> <1eca41df95ff660eb247a3de666adeb4@natalenko.name> <6AF8CEDE-2720-4206-900A-1A9B914A8FF0@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-7" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <6AF8CEDE-2720-4206-900A-1A9B914A8FF0@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Paolo Valente , Oleksandr Natalenko Cc: 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 , 'Paolo Valente' via bfq-iosched , Mark Brown List-Id: linux-mmc@vger.kernel.org On Wed, 2018-10-03 at 17:55 +-0200, Paolo Valente wrote: +AD4 The problem, in particular, is that bfq is a complex beast, fighting +AD4 against a jungle of I/O issues. You have to be really into bfq, even +AD4 to just know all of its features+ACE This is a problem by itself. I don't know anyone who wants to have to deal with I/O scheduler tunables. Bart.