Hi,
On Mon, Sep 25, 2000 at 03:47:03PM +0100, Alan Cox wrote:
>
> GFP_KERNEL has to be able to fail for 2.4. Otherwise you can get everything
> jammed in kernel space waiting on GFP_KERNEL and if the swapper cannot make
> space you die.
We already have PF_MEMALLOC to provide a last-chance allocation pool
which only the swapper can eat into.
The critical thing is to avoid having the swapper itself deadlock.
Everything revolves around that. Once you can make that guarantee,
it's perfectly safe to make GFP_KERNEL succeed for other callers, just
as long as you have enough beancounting in place in those callers.
Right now, the biggest obstacle to this is the GFP_ATOMIC behaviour:
/*
* Final phase: allocate anything we can!
*
* This is basically reserved for PF_MEMALLOC and
* GFP_ATOMIC allocations...
*/
Allowing GFP_ATOMIC to eat PF_MEMALLOC's last-chance pages is the
wrong thing to do if we want to guarantee swapper progress under
extreme load.
Cheers,
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
