From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754827AbcDMTyb (ORCPT ); Wed, 13 Apr 2016 15:54:31 -0400 Received: from mail-yw0-f195.google.com ([209.85.161.195]:35624 "EHLO mail-yw0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754813AbcDMTy0 (ORCPT ); Wed, 13 Apr 2016 15:54:26 -0400 Date: Wed, 13 Apr 2016 15:54:22 -0400 From: Tejun Heo To: Christoph Hellwig Cc: Linus Walleij , Paolo Valente , Jens Axboe , Fabio Checconi , Arianna Avanzini , linux-block@vger.kernel.org, "linux-kernel@vger.kernel.org" , Ulf Hansson , Mark Brown Subject: Re: [PATCH RFC 09/22] block, cfq: replace CFQ with the BFQ-v0 I/O scheduler Message-ID: <20160413195422.GE20142@htj.duckdns.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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160304173947.GA16764@infradead.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, Christoph. On Fri, Mar 04, 2016 at 09:39:47AM -0800, Christoph Hellwig wrote: > On Sat, Mar 05, 2016 at 12:29:39AM +0700, Linus Walleij wrote: > > 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? idk, are we gonna duplicate a full disk scheduler on blk-mq path? I think it'd be more sensible to make blk-mq call into the old elevator path for scheduling IOs on rotating rusts. Thanks. -- tejun