Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752154AbcCKLQr (ORCPT ); Fri, 11 Mar 2016 06:16:47 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:54501 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751743AbcCKLQk (ORCPT ); Fri, 11 Mar 2016 06:16:40 -0500 Date: Fri, 11 Mar 2016 03:16:36 -0800 From: Christoph Hellwig To: "Austin S. Hemmelgarn" Cc: Christoph Hellwig , Linus Walleij , Tejun Heo , 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: <20160311111636.GB3450@infradead.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> <56D9CF97.7080005@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56D9CF97.7080005@gmail.com> User-Agent: Mutt/1.5.24 (2015-08-30) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 768 Lines: 17 On Fri, Mar 04, 2016 at 01:10:31PM -0500, Austin S. Hemmelgarn wrote: > 1. This all started long before blk-mq hit mainline. Whoe cares? :) > 2. There's still a decent amount of block drivers that don't support blk-mq. > Last time I looked (around the time 4.4 came out), I saw the following that > either obviously don't support it, or are ambiguous as to whether they > support it or not. Here's a list of just the ones I know are being used on > existing systems running relatively recent kernel versions, not including There is no ambiguouity. You clearly named a few ones that aren't converted, but also a lot of make_request_fn based drivers which don't support any I/O scheduler. But that whole point is that anything actively developed should move over.