public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sched patch] more sync wakeups, 2.6.5-rc3-mm1
Date: Tue, 30 Mar 2004 22:38:02 +0200	[thread overview]
Message-ID: <20040330203802.GA5966@elte.hu> (raw)
In-Reply-To: <20040330185409.GA4214@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]


(patch attached now.)

* Ingo Molnar <mingo@elte.hu> wrote:

> the attached patch extends sync wakeups to the process sys_exit() path
> too: the chldwait wakeup can be done sync, since we know that the
> process is going to exit (and thus deschedule).
> 
> the most visible effect of this change is strace's behavior on SMP
> systems: it now stays on a single CPU, together with the traced child. 
> (previously it would run in parallel to the child, bouncing around
> madly.)
> 
> compiled & tested.
> 
> 	Ingo

[-- Attachment #2: sched-more-sync-wakeups.patch --]
[-- Type: text/plain, Size: 516 bytes --]

--- linux/kernel/signal.c.orig	
+++ linux/kernel/signal.c	
@@ -1386,12 +1386,12 @@ static inline void __wake_up_parent(stru
 	 * Fortunately this is not necessary for thread groups:
 	 */
 	if (p->tgid == tsk->tgid) {
-		wake_up_interruptible(&tsk->wait_chldexit);
+		wake_up_interruptible_sync(&tsk->wait_chldexit);
 		return;
 	}
 
 	do {
-		wake_up_interruptible(&tsk->wait_chldexit);
+		wake_up_interruptible_sync(&tsk->wait_chldexit);
 		tsk = next_thread(tsk);
 		if (tsk->signal != parent->signal)
 			BUG();

      reply	other threads:[~2004-03-30 20:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 18:54 [sched patch] more sync wakeups, 2.6.5-rc3-mm1 Ingo Molnar
2004-03-30 20:38 ` Ingo Molnar [this message]

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=20040330203802.GA5966@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /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