On Tue, 24 Apr 2007, Hugh Dickins wrote: > > And if a page is in the wrong area then it can be bounced before I/O > > is performed on it. > > I think that much is also true, but not where the problem lies. > Isn't the problem that filesystems using these block devices > expect their metadata to be accessible without kmap calls? Metadata is not movable nor subject to memory policies. It will never be mapped into a process space. - 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/
- References:
- Pagecache: find_or_create_page does not call a proper page allocator function
- From: Christoph Lameter <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Andrew Morton <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Christoph Lameter <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Andrew Morton <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Hugh Dickins <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Christoph Lameter <[email protected]>
- Re: Pagecache: find_or_create_page does not call a proper page allocator function
- From: Hugh Dickins <[email protected]>
- Pagecache: find_or_create_page does not call a proper page allocator function
- Prev by Date: Re: [patch] CFS scheduler, v3
- Next by Date: Re: [patch 1/4] Ignore stolen time in the softlockup watchdog
- 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):
 |