[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802271409480.13186@schroedinger.engr.sgi.com>
Date: Wed, 27 Feb 2008 14:11:19 -0800 (PST)
From: Christoph Lameter <clameter@....com>
To: Jason Gunthorpe <jgunthorpe@...idianresearch.com>
cc: Pete Wyckoff <pw@....edu>, Rik van Riel <riel@...hat.com>,
Andrea Arcangeli <andrea@...ranet.com>, a.p.zijlstra@...llo.nl,
izike@...ranet.com, Roland Dreier <rdreier@...co.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
Subject: Re: [ofa-general] Re: Demand paging for memory regions
On Wed, 13 Feb 2008, Jason Gunthorpe wrote:
> Christoph: It seemed to me you were first talking about
> freeing/swapping/faulting RDMA'able pages - but would pure migration
> as a special hardware supported case be useful like Catilan suggested?
That is a special case of the proposed solution. You could mlock the
regions of interest. Those can then only be migrated but not swapped out.
However, I think we need some limit on the number of pages one can mlock.
Otherwise the VM can get into a situation where reclaim is not possible
because the majority of memory is either mlocked or pinned by I/O etc.
--
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