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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 772F4C77B7E for ; Tue, 18 Apr 2023 22:06:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233167AbjDRWGD (ORCPT ); Tue, 18 Apr 2023 18:06:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45888 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231522AbjDRWGB (ORCPT ); Tue, 18 Apr 2023 18:06:01 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6E60A189; Tue, 18 Apr 2023 15:06:00 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 041FE6157B; Tue, 18 Apr 2023 22:06:00 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 85911C433D2; Tue, 18 Apr 2023 22:05:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1681855559; bh=4TzxYQM54gPj6fAMyI3AyBzp+dk5LpFT94Xr5/gjrX0=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=dxQBhdcrCQd5w9R2wn/07cf7rhZ8iADKh1CjHqyiIBLZHS/f7OVNSf/gt8KG0CR7h Oz4N9A9EESIVDc/zZIanRvYdJy6Kbh1WqoSbL45tIyDhAh0VZ2Gkw4aRGPne/24EZV EG4PhaKU8uuzDbgnkxxKnbzEtY58uWS7osG7BkGw= Date: Tue, 18 Apr 2023 15:05:57 -0700 From: Andrew Morton To: Catalin Marinas Cc: Justin Forbes , Mike Rapoport , Arnd Bergmann , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Geert Uytterhoeven , Guo Ren , John Paul Adrian Glaubitz , "Kirill A. Shutemov" , Max Filippov , Michael Ellerman , Rich Felker , Russell King , Will Deacon , Yoshinori Sato , Zi Yan , linux-arm-kernel@lists.infradead.org, linux-csky@vger.kernel.org, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-mm@kvack.org, linux-sh@vger.kernel.org, linux-xtensa@linux-xtensa.org, linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org Subject: Re: [PATCH v3 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Message-Id: <20230418150557.ea8c87c96ec64c899c88ab08@linux-foundation.org> In-Reply-To: References: <20230325060828.2662773-1-rppt@kernel.org> <20230325060828.2662773-3-rppt@kernel.org> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 12 Apr 2023 18:27:08 +0100 Catalin Marinas wrote: > > It sounds nice in theory. In practice. EXPERT hides too much. When you > > flip expert, you expose over a 175ish new config options which are > > hidden behind EXPERT. You don't have to know what you are doing just > > with the MAX_ORDER, but a whole bunch more as well. If everyone were > > already running 10, this might be less of a problem. At least Fedora > > and RHEL are running 13 for 4K pages on aarch64. This was not some > > accidental choice, we had to carry a patch to even allow it for a > > while. If this does go in as is, we will likely just carry a patch to > > remove the "if EXPERT", but that is a bit of a disservice to users who > > might be trying to debug something else upstream, bisecting upstream > > kernels or testing a patch. In those cases, people tend to use > > pristine upstream sources without distro patches to verify, and they > > tend to use their existing configs. With this change, their MAX_ORDER > > will drop to 10 from 13 silently. That can look like a different > > issue enough to ruin a bisect or have them give bad feedback on a > > patch because it introduces a "regression" which is not a regression > > at all, but a config change they couldn't see. > > If we remove EXPERT (as prior to this patch), I'd rather keep the ranges > and avoid having to explain to people why some random MAX_ORDER doesn't > build (keeping the range would also make sense for randconfig, not sure > we got to any conclusion there). Well this doesn't seem to have got anywhere. I think I'll send the patchset into Linus for the next merge window as-is. Please let's take a look at this Kconfig presentation issue during the following -rc cycle.