[PATCH v2 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text

public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed

From: Mike Rapoport <rppt@kernel•org>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Rich Felker <dalias@libc•org>,
	linux-ia64@vger•kernel.org, linux-sh@vger•kernel.org,
	Catalin Marinas <catalin.marinas@arm•com>,
	Max Filippov <jcmvbkbc@gmail•com>, Guo Ren <guoren@kernel•org>,
	linux-csky@vger•kernel.org, sparclinux@vger•kernel.org,
	Will Deacon <will@kernel•org>,
	Yoshinori Sato <ysato@users•sourceforge.jp>,
	Russell King <linux@armlinux•org.uk>,
	Geert Uytterhoeven <geert@linux-m68k•org>,
	Zi Yan <ziy@nvidia•com>,
	linux-xtensa@linux-xtensa•org, Arnd Bergmann <arnd@arndb•de>,
	linux-m68k@lists•linux-m68k.org,
	John Paul Adrian Glaubitz <glaubitz@physik•fu-berlin.de>,
	linux-arm-kernel@lists•infradead.org, linux-mm@kvack•org,
	linux-kernel@vger•kernel.org, Dinh Nguyen <dinguyen@kernel•org>,
	"Kirill A. Shutemov" <kirill.shutemov@linux•intel.com>,
	linuxppc-dev@lists•ozlabs.org,
	"David S. Miller" <davem@davemloft•net>,
	Mike Rapoport <rppt@kernel•org>
Subject: [PATCH v2 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text
Date: Fri, 24 Mar 2023 08:22:26 +0300	[thread overview]
Message-ID: <20230324052233.2654090-8-rppt@kernel.org> (raw)
In-Reply-To: <20230324052233.2654090-1-rppt@kernel.org>

From: "Mike Rapoport (IBM)" <rppt@kernel•org>

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.

Signed-off-by: Mike Rapoport (IBM) <rppt@kernel•org>
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux•intel.com>
---
 arch/nios2/Kconfig | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/arch/nios2/Kconfig b/arch/nios2/Kconfig
index 89708b95978c..fcaa6bbda3fc 100644
--- a/arch/nios2/Kconfig
+++ b/arch/nios2/Kconfig
@@ -45,16 +45,18 @@ menu "Kernel features"
 source "kernel/Kconfig.hz"
 
 config ARCH_FORCE_MAX_ORDER
-	int "Maximum zone order"
+	int "Order of maximal physically contiguous allocations"
 	range 8 19
 	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.
+
+	  Don't change if unsure.
 
 endmenu
 
-- 
2.35.1

next prev parent reply	other threads:[~2023-03-24  5:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24  5:22 [PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 01/14] arm: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 02/14] arm64: drop ranges in definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 03/14] arm64: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24 13:48   ` Zi Yan
2023-03-24  5:22 ` [PATCH v2 04/14] csky: drop ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 05/14] ia64: don't allow users to override ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 06/14] m68k: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24  5:22 ` Mike Rapoport [this message]
2023-03-24  5:22 ` [PATCH v2 08/14] nios2: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 09/14] powerpc: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 10/14] powerpc: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 11/14] sh: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24 14:28   ` Zi Yan
2023-03-24  5:22 ` [PATCH v2 12/14] sh: drop ranges for definition of ARCH_FORCE_MAX_ORDER Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 13/14] sparc: reword ARCH_FORCE_MAX_ORDER prompt and help text Mike Rapoport
2023-03-24  5:22 ` [PATCH v2 14/14] xtensa: " Mike Rapoport
2023-03-24 14:30 ` [PATCH v2 00/14] arch,mm: cleanup Kconfig entries for ARCH_FORCE_MAX_ORDER Zi Yan
2023-03-24 16:48   ` Mike Rapoport

find likely ancestor, descendant, or conflicting patches for this message:
( dfblob:89708b95978 dfblob:fcaa6bbda3f )
 OR (
bs:"[PATCH v2 07/14] nios2: reword ARCH_FORCE_MAX_ORDER prompt and help text" )
	(help)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230324052233.2654090-8-rppt@kernel.org \
    --to=rppt@kernel$(echo .)org \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=dalias@libc$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dinguyen@kernel$(echo .)org \
    --cc=geert@linux-m68k$(echo .)org \
    --cc=glaubitz@physik$(echo .)fu-berlin.de \
    --cc=guoren@kernel$(echo .)org \
    --cc=jcmvbkbc@gmail$(echo .)com \
    --cc=kirill.shutemov@linux$(echo .)intel.com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-csky@vger$(echo .)kernel.org \
    --cc=linux-ia64@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-m68k@lists$(echo .)linux-m68k.org \
    --cc=linux-mm@kvack$(echo .)org \
    --cc=linux-sh@vger$(echo .)kernel.org \
    --cc=linux-xtensa@linux-xtensa$(echo .)org \
    --cc=linux@armlinux$(echo .)org.uk \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=sparclinux@vger$(echo .)kernel.org \
    --cc=will@kernel$(echo .)org \
    --cc=ysato@users$(echo .)sourceforge.jp \
    --cc=ziy@nvidia$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox