From: Linus Torvalds <torvalds@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
mingo@elte.hu, kernel@kolivas.org, linux-kernel@vger.kernel.org,
piggin@cyberone.com.au, akpm@osdl.org, wli@holomorphy.com,
markw@osdl.org
Subject: Re: [PATCH] Performance regression in 2.6.7-rc3
Date: Tue, 15 Jun 2004 20:09:04 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0406152004540.4142@ppc970.osdl.org> (raw)
In-Reply-To: <E1BaPwX-0007k0-00@gondolin.me.apana.org.au>
On Wed, 16 Jun 2004, Herbert Xu wrote:
>
> Martin J. Bligh <mbligh@aracnet.com> wrote:
> >
> > How the hell can that have any effect on non-threaded workloads? Perhaps
> > some part of kernel compile *is* multi-threaded. It does seem to get
>
> make(1) with vfork(2) perhaps?
Very likely. And in the vfork() case it is definitely WRONG to try to
reschedule (either threads _or_ processes), since the parent is going to
go to sleep real soon now.
I think this code:
if (clone_flags & CLONE_VM)
wake_up_forked_thread(p);
else
wake_up_forked_process(p);
is just wrong, and it should be replaced with
wake_up_new_process(p, clone_flags);
and then "wake_up_new_process()" can do the right thing, which is
basically:
if (clone_flags & CLONE_VFORK)
synchronous wakeup, same as pipe-will-block case
else if (clone_flags & CLONE_VM)
thread-wakeup-case
else
process-wakeup-case
No?
Linus
next prev parent reply other threads:[~2004-06-16 3:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 0:28 Con Kolivas
2004-06-12 7:58 ` Nick Piggin
2004-06-15 4:56 ` Ingo Molnar
2004-06-15 13:11 ` Con Kolivas
2004-06-15 15:02 ` Martin J. Bligh
2004-06-16 2:14 ` Herbert Xu
2004-06-16 3:05 ` Nick Piggin
2004-06-16 3:10 ` Linus Torvalds
2004-06-16 3:18 ` Nick Piggin
2004-06-16 7:02 ` Ingo Molnar
2004-06-16 3:09 ` Linus Torvalds [this message]
2004-06-16 14:54 ` Martin J. Bligh
2004-06-16 3:00 ` Nick Piggin
2004-06-16 1:22 ` Con Kolivas
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.58.0406152004540.4142@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markw@osdl.org \
--cc=mbligh@aracnet.com \
--cc=mingo@elte.hu \
--cc=piggin@cyberone.com.au \
--cc=wli@holomorphy.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
all inboxes | Powered by JetHome®