Messages in this thread | | | Date | Fri, 7 Jan 2005 19:32:40 +0000 | From | Christoph Hellwig <> | Subject | Re: [RFC] per thread page reservation patch |
| |
On Fri, Jan 07, 2005 at 07:14:15PM +0000, Paulo Marques wrote: > This seems like a very asymmetrical behavior. If the code explicitly > reserves pages, it should explicitly use them, or it will become > impossible to track down who is using what (not to mention that this > will slow down every regular user of __alloc_pages, even if it is just > for a quick test). > > Why are there specialized functions to reserve the pages, but then they > are used through the standard __alloc_pages interface?
That seems to be the whole point of the patch, as that way it'll serve all sub-allocators or kernel function called by the user. Without this behaviour the caller could have simply used a mempool.
- 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/
| |