From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752513AbcCIGzp (ORCPT ); Wed, 9 Mar 2016 01:55:45 -0500 Received: from mail-wm0-f48.google.com ([74.125.82.48]:33901 "EHLO mail-wm0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751144AbcCIGzf convert rfc822-to-8bit (ORCPT ); Wed, 9 Mar 2016 01:55:35 -0500 Subject: Re: [PATCH RFC 09/22] block, cfq: replace CFQ with the BFQ-v0 I/O scheduler Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Content-Type: text/plain; charset=us-ascii From: Paolo Valente In-Reply-To: <20160304173947.GA16764@infradead.org> Date: Wed, 9 Mar 2016 07:55:28 +0100 Cc: Linus Walleij , Tejun Heo , Jens Axboe , Fabio Checconi , Arianna Avanzini , linux-block@vger.kernel.org, "linux-kernel@vger.kernel.org" , Ulf Hansson , Mark Brown Content-Transfer-Encoding: 8BIT Message-Id: <970CEAFA-1214-451B-9691-A3AEAD179D82@linaro.org> References: <1454364778-25179-1-git-send-email-paolo.valente@linaro.org> <1454364778-25179-10-git-send-email-paolo.valente@linaro.org> <20160211222210.GC3741@mtj.duckdns.org> <8FDE2B10-9BD2-4741-917F-5A37A74E5B58@linaro.org> <20160217170206.GU3741@mtj.duckdns.org> <72E81252-203C-4EB7-8459-B9B7060029C6@linaro.org> <20160301184656.GI3965@htj.duckdns.org> <20160304173947.GA16764@infradead.org> To: Christoph Hellwig X-Mailer: Apple Mail (2.1878.6) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il giorno 04/mar/2016, alle ore 18:39, Christoph Hellwig ha scritto: > On Sat, Mar 05, 2016 at 12:29:39AM +0700, Linus Walleij wrote: >> Hi Tejun, >> >> I'm doing a summary of this discussion as a part of presenting >> Linaro's involvement in Paolo's work. So I try to understand things. > > Btw, can someone explain why you guys waste so much time hacking and > arguing about a legacy codebase (old request code and I/O schedulers) > that everyone would really like to see disappear. Why don't you > spend your time on blk-mq where you have an entirely clean slate > for scheduling? I do agree that it would very important to deal with blk-mq. And much more difficult. IMHO, a clean way to proceed is to first try to improve bandwidth and latency guarantees in the simplest, single-queue case. Then to face the multi-queue case, leveraging the lessons learned in the single-queue case. Thanks, Paolo