From: Alexander Viro <viro@math.psu.edu>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: John Fremlin <chief@bandits.org>,
"Adam J. Richter" <adam@yggdrasil.com>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH(?): linux-2.4.4-pre2: fork should run child first
Date: Fri, 13 Apr 2001 22:51:25 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.21.0104132243190.26775-100000@weyl.math.psu.edu> (raw)
In-Reply-To: <Pine.LNX.4.31.0104131925370.11761-100000@penguin.transmeta.com>
On Fri, 13 Apr 2001, Linus Torvalds wrote:
>
>
> On 14 Apr 2001, John Fremlin wrote:
> >
> > . In fact, if you think
> > fork+exec is such a big performance hit why not go for spawn(2) and
> > have Linus and Al jump on you? ;-)
>
> spawn() is trivial to implement if you want to. I don't think it's all
> that much more interesting than vfork()+execve(), though.
Or faster, for that matter...
next prev parent reply other threads:[~2001-04-14 2:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-13 23:51 PATCH(?): linux-2.4.4-pre2: fork should run child first Adam J. Richter
2001-04-14 1:54 ` John Fremlin
2001-04-14 2:29 ` Linus Torvalds
2001-04-14 2:51 ` Alexander Viro [this message]
2001-04-14 2:52 ` Ulrich Drepper
-- strict thread matches above, loose matches on Subject: below --
2001-04-14 16:11 Adam J. Richter
2001-04-14 7:58 Adam J. Richter
2001-04-14 8:42 ` Michael O'Reilly
2001-04-14 9:00 ` Linus Torvalds
2001-04-14 15:06 ` Rik van Riel
2001-04-14 2:45 Adam J. Richter
2001-04-13 16:28 Hubertus Franke
2001-04-12 19:45 Adam J. Richter
2001-04-12 19:15 Adam J. Richter
2001-04-12 13:44 Hubertus Franke
2001-04-12 8:55 Adam J. Richter
2001-04-12 12:38 ` Horst von Brand
2001-04-17 9:15 ` Éric Brunet
2001-04-17 14:26 ` Jesse Pollard
2001-04-17 15:32 ` Éric Brunet
2001-04-13 21:08 ` John Fremlin
2001-04-14 3:53 ` Rik van Riel
2001-04-14 4:40 ` Linus Torvalds
2001-04-14 13:35 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.21.0104132243190.26775-100000@weyl.math.psu.edu \
--to=viro@math.psu.edu \
--cc=adam@yggdrasil.com \
--cc=chief@bandits.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).