Re: rfork() and copy on write

On 4/18/06, Walker, Bruce J (HP-Labs) <[email protected]> wrote:
> Yes and no.  The child has the same image as the parent (as in fork) and
> any changes made by either don't effect the other (the copy of write
> semantic).  So the semantics of rfork at identical to fork.  However,
> the implementation is to copy all the pages to the new node so the
> parent and child are not physically sharing the same page.
>
>

There is one optimization that would really help the performance but
compromise the availability. This is to make sure pages are pulled
from origin node only when needed. Similar to copy on write. But the
problem is that in that case we cannot afford to lose the origin node
even after process got migrated to a different node.

-aneesh


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642