linux-kernel - Re: -mm merge plans for 2.6.23

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0707111047040.14201@schroedinger.engr.sgi.com>
Date:	Wed, 11 Jul 2007 10:49:40 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Mel Gorman <mel@...net.ie>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: -mm merge plans for 2.6.23

On Wed, 11 Jul 2007, Mel Gorman wrote:

> I would like the patches to go through on the grounds that higher order
> allocations can succeed. However, I am also happy to say that order-0
> pages should be used as much as possible, that case should always be
> made as fast as possible and the world must not end if a high-order
> allocation fails.

SLUB can easily be made to not use higher order pages.

If the SLUB mobility patches are not merged then higher order page use 
can be explicitly enabled via passing the following to the kernel on boot

	slub_max_order=<desired max order>

If they are merged then the higher order page use can be disabled in case 
of trouble via

	slub_max_order=0
-
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/