On Sat, 15 Dec 2001, Rik van Riel wrote:
> > such scenarios can only be solved by using/creating independent pools,
> > and/or by using 'composite' pools like raid1.c does. One common
> OK, you've convinced me ...
> ... of the fact that you're reinventing Ben's reservation
> mechanism, poorly.
i have to admit that i did not know Ben's patch until today. I must have
missed it when he released it, and apparently there were no followup
releases(?). I now understand why Ben had to flame me. Anyway, here is his
With all respect, even if i had read it before, i'd have done mempool.c
the same way as it is now. (but i'd obviously have Cc:-ed Ben on it during
its development.) I'd like to sum up Ben's patch (Ben please correct me if
i misrepresent your patch in any way):
the patch adds a reservation feature to the page allocator. It defines a
'reservation structure', which causes the true free pages count of
particular page zones to be decreased artificially, thus creating a
virtual reserve of pages. These reservation structures can be assigned to
processes on a codepath basis. Eg. on IRQ entry the current process gets
assigned the IRQ-atomic reservation - and any original reservation is
restored on IRQ-exit. On swapping-code entry, arbitrary processes get the
swapping reservation. kswapd, kupdated and bdflush have their own,
permanent reservations. Freeing into the reserved pools is done by linking
the reservation structure to it's "home-zone", which the __free_pages()
code polls and refills. One process has a single active reservation
structure to allocate from.
this approach IMO does not answer some fundamental issues:
- Allocations might still fail with NULL. With mempool, allocations in
process contexts are guaranteed to always succeed.
- it does not allow the reservation of higher order allocations, which can
be especially important given the poor higher-order behavior of the page
- the reservation patch does not offer deadlock avoidance in critical code
paths with complex allocation patterns (see the examples from my
previous email). Just having separate pools of pages is not enough.
- minor nit #1: reservations are tied to zones, while mempool can take
from different zones, as long as the zones are compatible.
- minor nit #2: reservations are adding overhead to critical code areas
(and yes, besides oom-only code, the fast-path is touched as well) such
as rmqueue() and __free_pages(). Mempool does not add overhead to the
- perhaps there is a more advanced patch available (Ben?), but right now i
cannot see how the SLAB allocator can have the same reservation concept
added, without excessive code duplication.
Rik, it would be nice if you could provide a few technical arguments that
underscore your point. If i'm wrong then i'd like to be proven wrong.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:30 EST