diff options
| author | Mel Gorman <mgorman@suse.de> | 2011-05-11 16:29:33 +0100 |
|---|---|---|
| committer | Moyster <oysterized@gmail.com> | 2016-09-10 12:06:57 +0200 |
| commit | 13ffab6bbcfeedb9c125d934248ecebe8fdb7bd2 (patch) | |
| tree | 983cf0dec8357f8b7f73f7c47d03d58355b5704a /Documentation/vm | |
| parent | f9fa8fc6f8ff5fe10c4a83f361012dccc7de14f7 (diff) | |
mm: slub: Default slub_max_order to 0
To avoid locking and per-cpu overhead, SLUB optimisically uses
high-order allocations up to order-3 by default and falls back to
lower allocations if they fail. While care is taken that the caller
and kswapd take no unusual steps in response to this, there are
further consequences like shrinkers who have to free more objects to
release any memory. There is anecdotal evidence that significant time
is being spent looping in shrinkers with insufficient progress being
made (https://lkml.org/lkml/2011/4/28/361) and keeping kswapd awake.
SLUB is now the default allocator and some bug reports have been
pinned down to SLUB using high orders during operations like
copying large amounts of data. SLUBs use of high-orders benefits
applications that are sized to memory appropriately but this does not
necessarily apply to large file servers or desktops. This patch
causes SLUB to use order-0 pages like SLAB does by default.
There is further evidence that this keeps kswapd's usage lower
(https://lkml.org/lkml/2011/5/10/383).
Signed-off-by: Mel Gorman <mgorman@suse.de>
Signed-off-by: franciscofranco <franciscofranco.1990@gmail.com>
Diffstat (limited to 'Documentation/vm')
| -rw-r--r-- | Documentation/vm/slub.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/vm/slub.txt b/Documentation/vm/slub.txt index b0c6d1bbb..74a8b93ab 100644 --- a/Documentation/vm/slub.txt +++ b/Documentation/vm/slub.txt @@ -117,7 +117,7 @@ can be influenced by kernel parameters: slub_min_objects=x (default 4) slub_min_order=x (default 0) -slub_max_order=x (default 3 (PAGE_ALLOC_COSTLY_ORDER)) +slub_max_order=x (default 0) slub_min_objects allows to specify how many objects must at least fit into one slab in order for the allocation order to be acceptable. |