[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802081725200.5445@schroedinger.engr.sgi.com>
Date: Fri, 8 Feb 2008 17:27:03 -0800 (PST)
From: Christoph Lameter <clameter@....com>
To: Andrea Arcangeli <andrea@...ranet.com>
cc: Roland Dreier <rdreier@...co.com>, a.p.zijlstra@...llo.nl,
izike@...ranet.com, steiner@....com, linux-kernel@...r.kernel.org,
avi@...ranet.com, linux-mm@...ck.org, daniel.blueman@...drics.com,
Robin Holt <holt@....com>, general@...ts.openfabrics.org,
Andrew Morton <akpm@...ux-foundation.org>,
kvm-devel@...ts.sourceforge.net, Rik van Riel <riel@...hat.com>
Subject: Re: [ofa-general] Re: [patch 0/6] MMU Notifiers V6
On Sat, 9 Feb 2008, Andrea Arcangeli wrote:
> > Hmmmm.. that means we need something that actually pins pages for good so
> > that the VM can avoid reclaiming it and so that page migration can avoid
> > trying to migrate them. Something like yet another page flag.
>
> What's wrong with pinning with the page count like now? Dumb adapters
> would simply not register themself in the mmu notifier list no?
Pages will still be on the LRU and cycle through rmap again and again.
If page migration is used on those pages then the code may make repeated
attempt to migrate the page thinking that the page count must at some
point drop.
I do not think that the page count was intended to be used to pin pages
permanently. If we had a marker on such pages then we could take them off
the LRU and not try to migrate them.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists