On Tue, 24 Apr 2007, Hugh Dickins wrote: > I've not yet looked at the patch under discussion, but this remark > prompts me... a couple of days ago I got very worried by the various > hard-wired GFP_HIGHUSER allocations in mm/migrate.c and mm/mempolicy.c, > and wondered how those would work out if someone has a blockdev mmap'ed. I hope you are not confused by the fact that memory policies are only ever applied to one zone on a node. This is either HIGHMEM or NORMAL. There is no memory policy support for other than the highest zone. - 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/
- Follow-Ups:
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Hugh Dickins <hugh@veritas.com>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- References:
- Pagecache: find_or_create_page does not call a proper page allocator function
- From: Christoph Lameter <clameter@sgi.com>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Christoph Lameter <clameter@sgi.com>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Hugh Dickins <hugh@veritas.com>
- Pagecache: find_or_create_page does not call a proper page allocator function
- Prev by Date: Re: [patch] CFS scheduler, v3
- Next by Date: SMP lockup in virtualized environment
- Previous by thread: Re: Pagecache: find_or_create_page does not call a proper page allocator function
- Next by thread: Re: Pagecache: find_or_create_page does not call a proper page allocator function
- Index(es):
![]() |