Re: [PATCH 02/10] mm: system wide ALLOC_NO_WATERMARK

[Daniel Phillips <phillips@phunq.net>]

(What Peter already wrote, but in different words)

On Monday 06 August 2007 13:19, Christoph Lameter wrote:
> The solution may be as simple as configuring the reserves right and
> avoid the unbounded memory allocations.

Exactly.  That is what this patch set is about.  This is the part that 
provides some hooks to extend the traditional reserves to be able to 
handle some of the more difficult situations.

> That is possible if one 
> would make sure that the network layer triggers reclaim once in a
> while.

No.  It does no good at all for network to do a bunch of work 
reclaiming, then have some other random task (for example, a heavy 
writer) swoop in and grab the reclaimed memory before net can use it.  
Also, net allocates memory in interrupt context where shrink_caches is 
not possible.  The correct solution is to _reserve_ the memory net 
needs for vm writeout, which is in Peter's next patch set coming down 
the pipe.

Regards,

Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/