From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4794C00449 for ; Fri, 5 Oct 2018 09:49:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AFAA620652 for ; Fri, 5 Oct 2018 09:49:14 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AFAA620652 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ucw.cz Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728001AbeJEQrM (ORCPT ); Fri, 5 Oct 2018 12:47:12 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:39107 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727036AbeJEQrM (ORCPT ); Fri, 5 Oct 2018 12:47:12 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 868E980879; Fri, 5 Oct 2018 11:49:10 +0200 (CEST) Date: Fri, 5 Oct 2018 11:49:09 +0200 From: Pavel Machek To: Linus Walleij Cc: oleksandr@natalenko.name, Paolo Valente , Jens Axboe , linux-block , linux-mmc , linux-mtd@lists.infradead.org, Ulf Hansson , Richard Weinberger , Artem Bityutskiy , Adrian Hunter , Jan Kara , aherrmann@suse.com, mgorman@suse.com, Chunyan Zhang , "linux-kernel@vger.kernel.org" , bfq-iosched@googlegroups.com, Mark Brown Subject: Re: [PATCH] block: BFQ default for single queue devices Message-ID: <20181005094909.GB17069@amd> References: <20181002124329.21248-1-linus.walleij@linaro.org> <05fdbe23-ec01-895f-e67e-abff85c1ece2@kernel.dk> <1eca41df95ff660eb247a3de666adeb4@natalenko.name> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5I6of5zJg18YgZEa" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --5I6of5zJg18YgZEa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > On another hand, the users of embedded devices, mentioned by Linus, > > should already know what scheduler to choose because dealing with > > embedded world assumes the person can decide this on their own, or with > > the help of abovementioned udev scripts and/or Documentation/ as a > > reference point. > > > > So I see no obstacles here, and the choice to rely on udev by default > > sounds reasonable. > > >=20 > I am sorry but I do not agree with this. >=20 > There are several historical precedents where we have > concluded that just "have the kernel do the right thing > by default" is the way to go. Kernel should do the right thing by default, I agree with Linus W. Having reasonable defaults is useful; yes, my desktop has udev etc, but I still want reasonable scheduler when doing fsck in init=3D/bin/bash. Plus, I update kernels more often than distros, and I run various embedded stuff. Kernel should just provide reasonable defaults. And yes, we have "ionice" command and yes, it would be nice if it worked by default... Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --5I6of5zJg18YgZEa Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlu3M5UACgkQMOfwapXb+vJ6eACfcuqmLHOP0/KPd0GVpLGns0P0 WcIAoJmlmzUGDFB4GFpMdVF0osheZdbP =pxio -----END PGP SIGNATURE----- --5I6of5zJg18YgZEa--