On Tue, May 07, 2013 at 01:38:10PM +0200, Andrew Jones wrote:
> What about instead of adding a new syscall (remap_anon_pages) to
> instead extend mremap with new flags giving it a strict mode?
I actually thought about this and it's a very interesting argument.
When I thought about it, I felt the
Hi Isaku,
On Tue, May 07, 2013 at 07:07:40PM +0900, Isaku Yamahata wrote:
> On Mon, May 06, 2013 at 09:56:57PM +0200, Andrea Arcangeli wrote:
> > Hello everyone,
> >
> > this is a patchset to implement two new kernel features:
> > MADV_USERFAULT and remap_anon_pages.
> >
> > The combination of t
On Mon, May 06, 2013 at 09:56:57PM +0200, Andrea Arcangeli wrote:
>
> The current behavior of remap_anon_pages is very strict to avoid any
> chance of memory corruption going unnoticed, and it will return
> -EFAULT at the first sign of something unexpected (like a page already
> mapped in the dest
On Mon, May 06, 2013 at 09:56:57PM +0200, Andrea Arcangeli wrote:
> Hello everyone,
>
> this is a patchset to implement two new kernel features:
> MADV_USERFAULT and remap_anon_pages.
>
> The combination of the two features are what I would propose to
> implement postcopy live migration, and in g
Hello everyone,
this is a patchset to implement two new kernel features:
MADV_USERFAULT and remap_anon_pages.
The combination of the two features are what I would propose to
implement postcopy live migration, and in general demand paging of
remote memory, hosted in different cloud nodes with KSM.
