[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20200624221236.29560-1-jsavitz@redhat.com>
Date: Wed, 24 Jun 2020 18:12:36 -0400
From: Joel Savitz <jsavitz@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Joel Savitz <jsavitz@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Rafael Aquini <aquini@...hat.com>,
Fabrizio D'Angelo <fdangelo@...hat.com>, linux-mm@...ck.org,
trivial@...nel.org
Subject: [PATCH] mm/page_alloc: fix documentation error
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Matthew Wilcox <willy@...radead.org>
Cc: Rafael Aquini <aquini@...hat.com>
Cc: Fabrizio D'Angelo <fdangelo@...hat.com>
Cc: linux-mm@...ck.org
Cc: trivial@...nel.org
When I increased the upper bound of the min_free_kbytes value in
ee8eb9a5fe863, I forgot to tweak the above comment to reflect
the new value. This patch fixes that mistake.
Signed-off-by: Joel Savitz <jsavitz@...hat.com>
---
mm/page_alloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 48eb0f1410d4..e028b87ce294 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7832,7 +7832,7 @@ void setup_per_zone_wmarks(void)
* Initialise min_free_kbytes.
*
* For small machines we want it small (128k min). For large machines
- * we want it large (64MB max). But it is not linear, because network
+ * we want it large (256MB max). But it is not linear, because network
* bandwidth does not increase linearly with machine size. We use
*
* min_free_kbytes = 4 * sqrt(lowmem_kbytes), for better accuracy:
--
2.23.0
Powered by blists - more mailing lists