All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Dimitri Sivanich <sivanich@sgi.com>
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au, jbarnes@engr.sgi.com,
	hawkes@sgi.com, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Isolated sched domains for 2.6.8-rc2-mm1
Date: Sat, 31 Jul 2004 18:02:40 -0700	[thread overview]
Message-ID: <20040731180240.5dbd3887.akpm@osdl.org> (raw)
In-Reply-To: <20040730174651.GA14868@sgi.com>

Dimitri Sivanich <sivanich@sgi.com> wrote:
>
> Here's a version of the isolated scheduler domain code that I mentioned in an
>  RFC on 7/22.  This patch applies on top of 2.6.8-rc2-mm1 (to include all of
>  the new arch_init_sched_domain code).  This patch also contains the 2 line
>  fix to remove the check of first_cpu(sd->groups->cpumask)) that Jesse
>  sent in earlier.
> 
>  Note that this has not been tested with CONFIG_SCHED_SMT.  I hope that
>  my handling of those instances is OK.

It wasn't even compile-tested :(

diff -puN kernel/sched.c~sched-isolated-sched-domains-fix kernel/sched.c
--- 25/kernel/sched.c~sched-isolated-sched-domains-fix	2004-07-31 18:00:24.258057576 -0700
+++ 25-akpm/kernel/sched.c	2004-07-31 18:00:45.420840344 -0700
@@ -3861,7 +3861,7 @@ __init static void arch_init_sched_domai
 		if (i != first_cpu(this_sibling_map))
 			continue;
 
-		init_sched_build_groups(sched_group_cpus, this_sibling_mask,
+		init_sched_build_groups(sched_group_cpus, this_sibling_map,
 						&cpu_to_cpu_group);
 	}
 #endif
_


  reply	other threads:[~2004-08-01  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 17:46 [PATCH] Isolated sched domains for 2.6.8-rc2-mm1 Dimitri Sivanich
2004-08-01  1:02 ` Andrew Morton [this message]
2004-08-01 15:27   ` Dimitri Sivanich

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=20040731180240.5dbd3887.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ak@suse.de \
    --cc=hawkes@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nickpiggin@yahoo.com.au \
    --cc=sivanich@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.