The patch titled
Subject: Documentation/kernel-parameters.txt: update the default value of crashkernel low
has been removed from the -mm tree. Its filename was
documentation-update-the-default-value-of-crashkernel-low.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Baoquan He <bhe@xxxxxxxxxx>
Subject: Documentation/kernel-parameters.txt: update the default value of crashkernel low
In 94fb9334182284e8e7e4 ("x86/crash: Allocate enough low memory when
crashkernel=high") the default value of crashkernel low memory is changed
to 256M. In this patch update it accordingly.
Signed-off-by: Baoquan He <bhe@xxxxxxxxxx>
Cc: Joerg Roedel <jroedel@xxxxxxx>
Cc: Jonathan Corbet <corbet@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
Documentation/kernel-parameters.txt | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff -puN Documentation/kernel-parameters.txt~documentation-update-the-default-value-of-crashkernel-low Documentation/kernel-parameters.txt
--- a/Documentation/kernel-parameters.txt~documentation-update-the-default-value-of-crashkernel-low
+++ a/Documentation/kernel-parameters.txt
@@ -789,8 +789,10 @@ bytes respectively. Such letter suffixes
is passed, kernel could allocate physical memory region
above 4G, that cause second kernel crash on system
that require some amount of low memory, e.g. swiotlb
- requires at least 64M+32K low memory. Kernel would
- try to allocate 72M below 4G automatically.
+ requires at least 64M+32K low memory, also enough extra
+ low memory is needed to make sure DMA buffers for 32-bit
+ devices won't run out. Kernel would try to allocate at
+ at least 256M below 4G automatically.
This one let user to specify own low range under 4G
for second kernel instead.
0: to disable low allocation.
_
Patches currently in -mm which might be from bhe@xxxxxxxxxx are
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
