OS-4993: lx brand: vfork() should not be implemented in terms of fork()

Details

Issue Type:Bug
Priority:4 - Normal
Status:Resolved
Created at:2015-12-02T15:18:42.000Z
Updated at:2019-08-28T23:50:32.464Z

People

Created by:Former user
Reported by:Former user
Assigned to:Former user

Resolution

Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2015-12-02T21:24:03.000Z)

Fix Versions

2015-12-10 Dino (Release Date: 2015-10-12)

Related Issues

Labels

lxbrand

Description

In looking at the performance of a workload in production, it was revealed to be doing a modest amount of vfork()'ing and exec()'ing (~5/second) from a large Java process. However, because on LX vfork() is implemented in terms of fork() (and seems to have been since PSARC/2005/471 integrated in commit 9acbbeaf2a1ffe5c14b244867d427714fab43c5c), this is taking much, much longer than it should. We should implement vfork() natively (and indeed, we already do in the CLONE_VFORK case -- it seems that this should be a solvable problem.

Comments

Comment by Former user
Created at 2015-12-02T21:22:41.000Z

illumos-joyent commit 93c2b12 (branch master, by Jerry Jelinek)

OS-4993 lx brand: vfork() should not be implemented in terms of fork()
Reviewed by: Patrick Mooney <patrick.mooney@joyent.com>