| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 16 Dec 2011 14:23:50 +0100 From: Stanislaw Gruszka <sgruszka@...hat.com> To: David Rientjes <rientjes@...gle.com>, Andrew Morton <akpm@...ux-foundation.org> Cc: "Rafael J. Wysocki" <rjw@...k.pl>, linux-mm@...ck.org, linux-kernel@...r.kernel.org, Mel Gorman <mgorman@...e.de>, Andrea Arcangeli <aarcange@...hat.com>, Christoph Lameter <cl@...ux-foundation.org> Subject: [PATCH -mm] slub: debug_guardpage_minorder documentation tweak Signed-off-by: Stanislaw Gruszka <sgruszka@...hat.com> --- Documentation/ABI/testing/sysfs-kernel-slab | 6 ++++-- Documentation/vm/slub.txt | 7 ++++--- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/Documentation/ABI/testing/sysfs-kernel-slab b/Documentation/ABI/testing/sysfs-kernel-slab index bfd1d9f..91bd6ca 100644 --- a/Documentation/ABI/testing/sysfs-kernel-slab +++ b/Documentation/ABI/testing/sysfs-kernel-slab @@ -346,8 +346,10 @@ Description: number of objects per slab. If a slab cannot be allocated because of fragmentation, SLUB will retry with the minimum order possible depending on its characteristics. - When debug_guardpage_minorder > 0 parameter is specified, the - minimum possible order is used and cannot be changed. + When debug_guardpage_minorder=N (N > 0) parameter is specified + (see Documentation/kernel-parameters.txt), the minimum possible + order is used and this sysfs entry can not be used to change + the order at run time. What: /sys/kernel/slab/cache/order_fallback Date: April 2008 diff --git a/Documentation/vm/slub.txt b/Documentation/vm/slub.txt index dbf02ad..1514d9f 100644 --- a/Documentation/vm/slub.txt +++ b/Documentation/vm/slub.txt @@ -131,9 +131,10 @@ slub_min_objects. slub_max_order specified the order at which slub_min_objects should no longer be checked. This is useful to avoid SLUB trying to generate super large order pages to fit slub_min_objects of a slab cache with -large object sizes into one high order page. Setting parameter -debug_guardpage_minorder > 0 forces setting slub_max_order to 0, what -cause minimum possible order of slabs allocation. +large object sizes into one high order page. Setting command line +parameter debug_guardpage_minorder=N (N > 0), forces setting +slub_max_order to 0, what cause minimum possible order of slabs +allocation. SLUB Debug output ----------------- -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists