On 1/14/13 8:43 AM, Benoit Jacob wrote:
Right and I didn't understand how it could tell when it has to subsequently actually allocate memory when a write is made into these pages. Got my answer offline: it's a page fault.
Yup. The classic example in OS land is optimizing fork() via copy-on-write... The parent and child processes initially share the same physical memory pages, eliminating the need to duplicate everything immediately upon creation of the child (which would often be wasted effort, such as in the common fork-and-exec pattern).
http://en.wikipedia.org/wiki/Copy-on-write Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
