Rik van Riel wrote:
I think that maybe for 2.6.22 we should just alias MADV_FREE to run with the MADV_DONTNEED functionality, so that the glibc people can make the change on their side while we figure out what will be the best thing to do on the kernel side.
No need for that. We can later extend glibc to use MADV_FREE and fall back on MADV_DONTNEED.
-- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Rik van Riel <[email protected]>
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- References:
- [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Rik van Riel <[email protected]>
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Nick Piggin <[email protected]>
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Ulrich Drepper <[email protected]>
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Nick Piggin <[email protected]>
- Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- From: Rik van Riel <[email protected]>
- [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- Prev by Date: Re: [PATCH 2/7] [RFC] Common power driver for Linux gadgets
- Next by Date: Re: Back to the future.
- Previous by thread: Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- Next by thread: Re: [PATCH] MM: implement MADV_FREE lazy freeing of anonymous memory
- Index(es):
 |