[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802081813300.5602@schroedinger.engr.sgi.com>
Date: Fri, 8 Feb 2008 18:16:16 -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:
> The VM shouldn't break if try_to_unmap doesn't actually make the page
> freeable for whatever reason. Permanent pins shouldn't happen anyway,
VM is livelocking if too many page are pinned that way right now. The
higher the processors per node the higher the risk of livelock because
more processors are in the process of cycling through pages that have an
elevated refcount.
> so defining an ad-hoc API for that doesn't sound too appealing. Not
> sure if old hardware deserves those special lru-size-reduction
> optimizations but it's not my call (certainly swapoff/mlock would get
> higher priority in that lru-size-reduction area).
Rik has a patchset under development that addresses issues like this. The
elevated refcount pin problem is not really relevant to the patchset we
are discussing here.
--
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