Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1EC40C61DA4 for ; Fri, 27 Jan 2023 20:11:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230324AbjA0ULD (ORCPT ); Fri, 27 Jan 2023 15:11:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56232 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230072AbjA0UKq (ORCPT ); Fri, 27 Jan 2023 15:10:46 -0500 Received: from mail-pj1-x1033.google.com (mail-pj1-x1033.google.com [IPv6:2607:f8b0:4864:20::1033]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24B9B298DB for ; Fri, 27 Jan 2023 12:10:11 -0800 (PST) Received: by mail-pj1-x1033.google.com with SMTP id h5-20020a17090a9c0500b0022bb85eb35dso5754135pjp.3 for ; Fri, 27 Jan 2023 12:10:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=mCpGCS/OXeh7kYIrLqMAqyzZU6U0iWsXPrIDck1yl4Q=; b=COEuRwnZJeTT8Co7vP68ncETJxbQLPH3GL04G1l4xtc63Ci7eG+N0f+/2YFHeMBD7x 4eGGkPJ+XjN1GOtuK0cGDhBn+/PVNG9Y+tEuOjZSrgJNnMnpcfp5RoNSJAJkiBl28aaF lFFPh7iOrLVR+Fhpn0Maam7MFveM7j4k2BPH+QfcrWLWhtnL002SwNczYu26N4pNjBx9 K30t9T2hSJ2k/sSlHZgz4qmJfX4W36AdPYARXp6KRm4JryEMJXwx1BlrF2f6kMNs+841 sRs16HWRnMCHKY7XAUWOib0j+nlA+ujPX6XdCsgqNqo5rDXhQOKWoGrBrliXuHOvhLEg tkbA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=mCpGCS/OXeh7kYIrLqMAqyzZU6U0iWsXPrIDck1yl4Q=; b=660Y1XV5w0R2lgXSQkEBDc3aCK5BOvsd+197gIwjLmKnBshStQTogxux+wmc+45Bhs JrveB0glpLAhykCpJa7TCbfJUSfZlvJY+XGYNUl+rpdiWP8YUzTIAra3GLOejTLQCaN7 F6LmyNMQ/a9hFxH8FYiHLXKXVUDWyK979qAym5S5ZvkppRqs3Jy+rZJaK6YUSddZHjhz 9JBJxdUfkuU2pguKKX3y0HLy0VpTBQKVFXJ8UyaLGZ79ekIy0bUadaoBjuYPml+Q0NgR XUXlON3u7j8M+DZ7xdkZRxtc5vglU8iq3qI/aHJuRjP9PThMXDTiSoW/ztvd8vGUXmn0 l0kg== X-Gm-Message-State: AFqh2kp1+4YTb13wfVg4ZxNdoEL4Gjq1clgTi4Gdtyz+FsMckklu8F30 AKbH6JKj5jhOPbiYlZdHt2ndCA== X-Google-Smtp-Source: AMrXdXue43UUcDKwZjZdhWr+oBt+sdwXQSo5OBklKDMWMoPNfYRjlup1uXivGzXJ5OIlbz0SonbxTQ== X-Received: by 2002:a17:902:7611:b0:192:5a90:b047 with SMTP id k17-20020a170902761100b001925a90b047mr10038582pll.3.1674850210540; Fri, 27 Jan 2023 12:10:10 -0800 (PST) Received: from [192.168.1.136] ([198.8.77.157]) by smtp.gmail.com with ESMTPSA id s10-20020a17090a760a00b0022bbbba9801sm5295775pjk.37.2023.01.27.12.10.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Jan 2023 12:10:09 -0800 (PST) Message-ID: <3ba1adc6-4fb4-036c-8eca-91f549471c49@kernel.dk> Date: Fri, 27 Jan 2023 13:10:08 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Subject: Re: [PATCH] block: Default to build the BFQ I/O scheduler Content-Language: en-US To: Ulf Hansson Cc: linux-block@vger.kernel.org, Paolo Valente , Linus Walleij , linux-kernel@vger.kernel.org References: <20230127154339.157460-1-ulf.hansson@linaro.org> <5743fb1b-eb4b-d169-a467-ee618bcd75f5@kernel.dk> From: Jens Axboe In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/27/23 8:58 AM, Ulf Hansson wrote: > On Fri, 27 Jan 2023 at 16:48, Jens Axboe wrote: >> >> On 1/27/23 8:43 AM, Ulf Hansson wrote: >>> Today BFQ is widely used and it's also the default choice for some of the >>> single-queue-based storage devices. Therefore, let's make it more >>> convenient to build it as default, along with the other I/O schedulers. >>> >>> Let's also build the cgroup support for BFQ as default, as it's likely that >>> it's wanted too, assuming CONFIG_BLK_CGROUP is also set, of course. >> >> This won't make much of a difference, when the symbols are already in >> the .config. So let's please not. It may be a 'y' for you by default, >> but for lots of others it is not. Don't impose it on folks. > > This isn't about folkz, but HW. :-) Is it everybody? No, it's a subset. Everybody adding a new driver wants to default to y/m, and it's almost always wrong. > I was thinking that it makes sense for the similar reason to why kyber > and deadline are being built as default. Or are there any particular > other reasons to why we build those in as default, but not BFQ? deadline arguably makes sense as it's simple, and we should have one default scheduler. kyber probably does not need to be default y. But at least that one doesn't pull in other dependencies. -- Jens Axboe