Messages in this thread | | | Subject | Re: [RFC] mempool_alloc() pre-allocated object usage | From | Arjan van de Ven <> | Date | Mon, 03 Oct 2005 16:49:13 +0200 |
| |
On Mon, 2005-10-03 at 17:36 +0300, Paul Mundt wrote:
> Both usage patterns seem valid from my point of view, would you be open > to something that would accomodate both? (ie, possibly adding in a flag > to determine pre-allocated object usage?) Or should I not be using > mempool for contiguity purposes?
a similar dillema was in the highmem bounce code in 2.4; what worked really well back then was to do it both; eg use half the pool for "immediate" use, then try a VM alloc, and use the second half of the pool for the really emergency cases.
Technically a mempool is there ONLY for the fallback, but I can see some value in making it also a fastpath by means of a small scratch pool
- 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/
| |