> What is the behaviour of someone setting VM_DONTCOPY on memory that was
> copy on write between a large number of processes (say an executable
> image) ? Don't copy - but don't copy from what, from the original
> mapping or from the COW mapping of the original mapping ?
it would result in a VM 'hole' - completely unmapped virtual memory with
no vma backing it.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/