Depends on your point of view.
Now that we have the mechanism for clone(2), we can give Linux vfork(2)
can-be-relied-upon semantics -- we're able to guarantee that the memory
spaces are shared until the next exec(2). Assuming you're using a
recent enough kernel, that is. It would make most sense implemented as
another flag to clone(2), so it fails with an older kernel.
vfork would probably be _slightly_ faster, because there would be no
need to copy the VMA list and one TLB flush could be skipped assuming
one context switch before the exec(2).
I don't actually recommend this, however. vfork == fork seems cleanest
to me.
-- Jamie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/