Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034009AbcJ0Pzj (ORCPT ); Thu, 27 Oct 2016 11:55:39 -0400 Received: from mout.kundenserver.de ([212.227.126.131]:59033 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934561AbcJ0Pzh (ORCPT ); Thu, 27 Oct 2016 11:55:37 -0400 Date: Thu, 27 Oct 2016 17:55:33 +0200 From: Heinz Diehl To: linux-kernel@vger.kernel.org Subject: Re: [PATCH 00/14] introduce the BFQ-v0 I/O scheduler as an extra scheduler Message-ID: <20161027155533.GA4761@fritha.org> References: <1477474082-2846-1-git-send-email-paolo.valente@linaro.org> <20161026113443.GA13587@quack2.suse.cz> <4ed3e291-b3e5-5ee3-6838-58644bd3d99b@sandisk.com> <12386463.fJy0cVexVD@wuerfel> <20161026152955.GA21262@infradead.org> <3ebadbb8-9ac2-851a-66f9-c9db25713695@kernel.dk> <38156FA7-9A66-44DC-8D0C-28F149D1E49B@linaro.org> <09fc1e06-3fd6-b13d-0dd9-0edfb55b01d1@kernel.dk> <20161027092656.GD19743@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Accept-Language: no,dk,se,en,de Organization: private site OpenPGP: id=60F4A92C; url=http://www.fritha.org/htd.asc; preference=signencrypt User-Agent: Mutt/1.7.1+7 (a3e35631b503) (2016-10-04) X-Provags-ID: V03:K0:7xC3+8QGx3KF4dKHIr9Br26iiy+c2usK/t+mhREQYp19p3ACkC1 Yr6iI01Upv89XeOiO3bIRJEJc9Sq4ccHfm+vux+0j55mhewV9fiCxyfaAGmEHaRLDK6V2Dp 2rPUB0YPbqEOVfmwFvBxWKXyD3yoUV3hepyd5fIiF5BflmacpffpqIVZ2wnm8NnBzRxxJH2 KzrdiQdlouSYjjqyq38KQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:xo3Wf8GTaiI=:Cb40hgKt8VofH2vOZ2UOm1 bMSPT9c6NyajFOwBrjog4PmTmDsQYJ9+zmRBhrCywqJnb03afLElH8nE3YJWQgsnUxxmHWUpX Ej0ptyzXrbE9hsUkwl1Go1rLXwrj8wJ+3tMkTFxCt9uFxqhZidw4czm67Udja0xImBtkEGNcq WWjXWhwRNMrq9a103ZU3J330fv9+49N0ujxof9W6pgBPLdtgY8xC4jyazUh5PBp05u828sXUS gJ30T+I2dy5I1XLdPMobRY/jgNGAqFjOq9JMUQa0bj5GpwP82ibr5mZsKVxR7i33akXuiAtoo nghJEQYd8+GW5yOWQd1+cG+TitFunFeU9QcygBraiPT0SXEVjnMpaYNU5D0IyW1OG1W6pzPNf 37I+tfuVBYayX6oSrCVNI0v2bRrriXfXWdKKKTtW8tzH2tpSNneI3xMm87Zj0Q1osv+6vD4y/ 9XqHDN/VMlm4aot+RyALby8QJvUrP5ftOx0NOoMK42oxXQLGdw9UIhcoi+jtf+LkhKhe2H50U yI2ZXqd5Z1xpdd+9+6qsgbEo+CHVJlrnlGMX8tD6Inx2Mn/v0KeKQR8Tol5tXTVcKnlaR0EGA y+B1/6RPLcTy585pwTbneLrnwbo1D++75JwLcIgtyOJgrMzGDYn9VOsyHvFxo59kXSsbFd0RN R5s37gbYZj3d2izaXzFrOtkB4xidh6cjHk0bCbcrNee9YL2/t+pc3im/uo5M0y7aZITg= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1246 Lines: 32 On 27.10.2016, Grozdan wrote: > So in the end, I'm here to support the inclusion of BFQ. Paolo has put > too much energy, time, and sleepless nights into this so people like > me can have a working, responsive system during heavy disk operations. > From a normal user's perspective, I do not want BFQ to be dismissed > and all the effort/time/etc thrown out the window. From my > perspective, Paolo deserves more support from the guys in charge of > the block layer in Linux. I really want to second that! Just take a bog-standard desktop PC with an SSD and a reasonably fast CPU (an 8-core Xeon in my case) and do the following: 1. dd if=/dev/zero of=deleteme bs=1M count=50000 2. Start oowriter (Libreoffice Writer) Using both cfq, deadline or noop, oowriter does not load until dd'ing the 50 gigs is finished. Using bfq, oowriter loads nearly immediately. Not to mention that both cfq, deadline and noop are a nightmare on Android in terms of latency. I'm (obviously) neither a kernel nor a bfq developer, but I really want you to reconsider, with the overall greatness of bfq in mind, if it really is totally impossible to include it at least as a scheduler option, alongside the other three already existing ones. Thanks, Heinz