Messages in this thread | | | Date | Mon, 13 Feb 2006 22:05:46 +0200 | From | "Michael S. Tsirkin" <> | Subject | Re: Re: madvise MADV_DONTFORK/MADV_DOFORK |
| |
Quoting Linus Torvalds <torvalds@osdl.org>: > I would suggest that if you wanted to be very careful, you'd simply > disallow changing - or perhaps just clearing - that DONTCOPY flag on > special regions (ie ones that have been marked with VM_IO or VM_RESERVED).
Right, this was already proposed here http://lkml.org/lkml/2005/11/3/81 and I site: > You're then saying that a process cannot set VM_DONTCOPY on a VM_IO > area to prevent the first child getting the area, but clear it after > so the next child does get a copy of the area. I think it'd be wrong > (surprising) to limit the functionality in that way.
-- Michael S. Tsirkin Staff Engineer, Mellanox Technologies - 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/
| |