From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Vlastimil Babka <vbabka@suse.cz>, Mel Gorman <mgorman@suse.de>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-doc@vger.kernel.org
Subject: [patch -mm] mm, page_alloc: extend kernelcore and movablecore for percent fix
Date: Tue, 13 Feb 2018 17:00:50 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1802131700160.71590@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1802131651140.69963@chino.kir.corp.google.com>
Specify that movablecore= can use a percent value.
Remove comment about hugetlb pages not being movable per Mike.
Cc: Mike Kravetz <mike.kravetz@oracle.com>
Signed-off-by: David Rientjes <rientjes@google.com>
---
.../admin-guide/kernel-parameters.txt | 22 +++++++++----------
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -1837,10 +1837,9 @@
ZONE_MOVABLE is used for the allocation of pages that
may be reclaimed or moved by the page migration
- subsystem. This means that HugeTLB pages may not be
- allocated from this zone. Note that allocations like
- PTEs-from-HighMem still use the HighMem zone if it
- exists, and the Normal zone if it does not.
+ subsystem. Note that allocations like PTEs-from-HighMem
+ still use the HighMem zone if it exists, and the Normal
+ zone if it does not.
It is possible to specify the exact amount of memory in
the form of "nn[KMGTPE]", a percentage of total system
@@ -2353,13 +2352,14 @@
mousedev.yres= [MOUSE] Vertical screen resolution, used for devices
reporting absolute coordinates, such as tablets
- movablecore=nn[KMG] [KNL,X86,IA-64,PPC] This parameter
- is similar to kernelcore except it specifies the
- amount of memory used for migratable allocations.
- If both kernelcore and movablecore is specified,
- then kernelcore will be at *least* the specified
- value but may be more. If movablecore on its own
- is specified, the administrator must be careful
+ movablecore= [KNL,X86,IA-64,PPC]
+ Format: nn[KMGTPE] | nn%
+ This parameter is the complement to kernelcore=, it
+ specifies the amount of memory used for migratable
+ allocations. If both kernelcore and movablecore is
+ specified, then kernelcore will be at *least* the
+ specified value but may be more. If movablecore on its
+ own is specified, the administrator must be careful
that the amount of memory usable for all allocations
is not too small.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-14 1:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 0:24 [patch 1/2] mm, page_alloc: extend kernelcore and movablecore for percent David Rientjes
2018-02-13 0:24 ` [patch 2/2] mm, page_alloc: move mirrored_kernelcore to __meminitdata David Rientjes
2018-02-13 23:46 ` [patch 1/2] mm, page_alloc: extend kernelcore and movablecore for percent Andrew Morton
2018-02-13 23:55 ` David Rientjes
2018-02-14 1:14 ` Andrew Morton
2018-02-14 0:37 ` Mike Kravetz
2018-02-14 0:53 ` David Rientjes
2018-02-14 1:00 ` David Rientjes [this message]
2018-02-14 1:10 ` [patch -mm] mm, page_alloc: extend kernelcore and movablecore for percent fix Mike Kravetz
2018-02-14 9:59 ` [patch 1/2] mm, page_alloc: extend kernelcore and movablecore for percent Michal Hocko
2018-02-14 10:28 ` David Rientjes
2018-02-15 14:45 ` Michal Hocko
2018-02-15 15:11 ` Matthew Wilcox
2018-02-15 15:49 ` Christopher Lameter
2018-02-15 20:14 ` Matthew Wilcox
2018-02-16 15:41 ` Christopher Lameter
2018-02-15 20:48 ` Matthew Wilcox
2018-02-16 0:45 ` David Rientjes
2018-02-16 15:44 ` Christopher Lameter
2018-02-16 16:01 ` Matthew Wilcox
2018-02-16 16:08 ` Christopher Lameter
2018-02-16 17:09 ` Matthew Wilcox
2018-02-15 20:47 ` David Rientjes
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=alpine.DEB.2.10.1802131700160.71590@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mike.kravetz@oracle.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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