From: Linus Torvalds <torvalds@transmeta.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "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 21:40:16 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.31.0104132138310.24573-100000@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104140049360.12164-100000@imladris.rielhome.conectiva>
On Sat, 14 Apr 2001, Rik van Riel wrote:
>
> Also, have you managed to find a real difference with this?
It actually makes a noticeable difference on lmbench, so I think adam is
100% right.
> If it turns out to be beneficial to run the child first (you
> can measure this), why not leave everything the same as it is
> now but have do_fork() "switch threads" internally ?
Probably doesn't much matter. We've invalidated the TLB anyway due to the
page table copy, so the cost of switching the MM is not all that
noticeable.
Linus
next prev parent reply other threads:[~2001-04-14 5:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 8:55 PATCH(?): linux-2.4.4-pre2: fork should run child first 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 [this message]
2001-04-14 13:35 ` Rik van Riel
2001-04-12 13:44 Hubertus Franke
2001-04-12 19:15 Adam J. Richter
2001-04-12 19:45 Adam J. Richter
2001-04-13 16:28 Hubertus Franke
2001-04-13 23:51 Adam J. Richter
2001-04-14 1:54 ` John Fremlin
2001-04-14 2:29 ` Linus Torvalds
2001-04-14 2:51 ` Alexander Viro
2001-04-14 2:52 ` Ulrich Drepper
2001-04-14 2:45 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 16:11 Adam J. Richter
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.LNX.4.31.0104132138310.24573-100000@cesium.transmeta.com \
--to=torvalds@transmeta.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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).