lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 09 Sep 2009 12:59:31 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Theodore Tso <tytso@....edu>, mingo@...hat.com, hpa@...or.com,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	efault@....de, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched: Turn off child_runs_first

On 09/09/2009 12:08 PM, Ingo Molnar wrote:
> 
> * Theodore Tso <tytso@....edu> wrote:

>> Wasn't one of the reasons why we historically did child_runs_first 
>> was so that for fork/exit workloads, the child has a chance to 
>> exec the new process?  If the parent runs first, then more pages 
>> will probably need to be COW'ed.
> 
> That kind of workload should be using vfork() anyway, and be even 
> faster because it can avoid the fork overhead, right?

According to my man page, POSIX.1-2008 removes the specification  of
vfork().

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ