Re: [RFC] Changing COW detection to be memory hotplug friendly

[Dave Hansen]

On Thu, 2005-02-10 at 20:05 +0100, Andrea Arcangeli wrote:
> Overall I see nothing wrong in preventing memory removal while rawio is
> in flight. rawio cannot be in flight forever (ptrace and core dump as
> well should complete eventually). Why can't you simply drop pages from
> the freelist one by one until all of them are removed from the freelist?

We actually do that, in addition to the more active methods of capturing
the memory that we're about to remove.

You're right, I don't really see a problem with ignoring those pages, at
least in the active migration code.  We would, of course, like to keep
the number of things that we depend on good faith to get migrated to a
minimum, but things under I/O are the least of our problems.

The only thing we might want to do is put something in the rawio code to
look for the PG_capture pages to ensure that it gives the migration code
a shot at them every once in a while (when I/O is not in flight,
obviously).

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/