Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752558AbdCEPZ4 (ORCPT ); Sun, 5 Mar 2017 10:25:56 -0500 Received: from mail-pf0-f173.google.com ([209.85.192.173]:34088 "EHLO mail-pf0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752162AbdCEPZy (ORCPT ); Sun, 5 Mar 2017 10:25:54 -0500 Subject: Re: [PATCH RFC 01/14] block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler To: Paolo Valente , Tejun Heo References: <20170304160131.57366-1-paolo.valente@linaro.org> <20170304160131.57366-2-paolo.valente@linaro.org> Cc: Fabio Checconi , Arianna Avanzini , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, ulf.hansson@linaro.org, linus.walleij@linaro.org, broonie@kernel.org From: Jens Axboe Message-ID: <91b856e8-2c14-00b6-fdd8-b9879b1b9952@kernel.dk> Date: Sun, 5 Mar 2017 08:16:20 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <20170304160131.57366-2-paolo.valente@linaro.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1092 Lines: 24 On 03/04/2017 09:01 AM, Paolo Valente wrote: > We tag as v0 the version of BFQ containing only BFQ's engine plus > hierarchical support. BFQ's engine is introduced by this commit, while > hierarchical support is added by next commit. We use the v0 tag to > distinguish this minimal version of BFQ from the versions containing > also the features and the improvements added by next commits. BFQ-v0 > coincides with the version of BFQ submitted a few years ago [1], apart > from the introduction of preemption, described below. > > BFQ is a proportional-share I/O scheduler, whose general structure, > plus a lot of code, are borrowed from CFQ. I'll take a closer look at this in the coming week. But one quick comment - don't default to BFQ. Both because it might not be fully stable yet, and also because the performance limitation of it is quite severe. Whereas deadline doesn't really hurt single queue flash at all, BFQ will. Generally, I think that sort of logic should go into a udev rule. If a device is rotational it should default to BFQ once the dust has settled. -- Jens Axboe