From nobody Sun Feb 8 10:49:03 2026 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 BFA78C77B62 for ; Sat, 25 Mar 2023 06:10:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231946AbjCYGKG (ORCPT ); Sat, 25 Mar 2023 02:10:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55484 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232233AbjCYGJj (ORCPT ); Sat, 25 Mar 2023 02:09:39 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB5B113DC9; Fri, 24 Mar 2023 23:09:29 -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 3C49E601D7; Sat, 25 Mar 2023 06:09:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 09077C433EF; Sat, 25 Mar 2023 06:09:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1679724568; bh=hj7vE83HssbFqh7ceXf4d8PDT2ibdeflIODgz+GdCho=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=SXe80G8K5kFrxjG4CHAB7R5j4HsXAkKtMPBiJa2K7KINUPXIi2Ttz6jVYYud+uQQu Sqk9QUfeacGt5ZgjN99doqzQVrC50C3YuLYQNcpirr0Ia10vnSKBcxUodmHH52wRjn YgaNoaLS/WzDEARfuG9phgmsGvIt528St1Sl/tGvK/A5j/ONumaKl9G/hpq8SZMPd4 tM55ZAcYgEJKLtK8ZxDvTirG9+OhUOJ2sGiPwsl3qPQhNSxborInoPqSn1guhYdrVl uogAfsplBhSxkmeDSpnuy73jioEoJrClCNpR9seAZETVm5kYNiqhYCXq7K8iz0f3D9 rJ2AfmxVuTIig== From: Mike Rapoport To: Andrew Morton Cc: Arnd Bergmann , Catalin Marinas , Christophe Leroy , "David S. Miller" , Dinh Nguyen , Geert Uytterhoeven , Guo Ren , John Paul Adrian Glaubitz , "Kirill A. Shutemov" , Max Filippov , Michael Ellerman , Mike Rapoport , 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: [PATCH v3 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text Date: Sat, 25 Mar 2023 09:08:20 +0300 Message-Id: <20230325060828.2662773-7-rppt@kernel.org> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20230325060828.2662773-1-rppt@kernel.org> References: <20230325060828.2662773-1-rppt@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" From: "Mike Rapoport (IBM)" The prompt and help text of ARCH_FORCE_MAX_ORDER are not even close to describe this configuration option. Update both to actually describe what this option does. Acked-by: Kirill A. Shutemov Acked-by: Geert Uytterhoeven Reviewed-by: Zi Yan Signed-off-by: Mike Rapoport (IBM) --- arch/m68k/Kconfig.cpu | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu index c9df6572133f..e530bc8f240f 100644 --- a/arch/m68k/Kconfig.cpu +++ b/arch/m68k/Kconfig.cpu @@ -398,21 +398,23 @@ config SINGLE_MEMORY_CHUNK Say N if not sure. =20 config ARCH_FORCE_MAX_ORDER - int "Maximum zone order" if ADVANCED + int "Order of maximal physically contiguous allocations" if ADVANCED depends on !SINGLE_MEMORY_CHUNK default "10" help - The kernel memory allocator divides physically contiguous memory - blocks into "zones", where each zone is a power of two number of - pages. This option selects the largest power of two that the kernel - keeps in the memory allocator. If you need to allocate very large - blocks of physically contiguous memory, then you may need to - increase this value. + The kernel page allocator limits the size of maximal physically + contiguous allocations. The limit is called MAX_ORDER and it + defines the maximal power of two of number of pages that can be + allocated as a single contiguous block. This option allows + overriding the default setting when ability to allocate very + large blocks of physically contiguous memory is required. =20 For systems that have holes in their physical address space this value also defines the minimal size of the hole that allows freeing unused memory map. =20 + Don't change if unsure. + config 060_WRITETHROUGH bool "Use write-through caching for 68060 supervisor accesses" depends on ADVANCED && M68060 --=20 2.35.1