From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Question on build_sched_domains
Date: Sat, 25 Mar 2006 14:06:19 +0530 [thread overview]
Message-ID: <20060325083619.GC17011@in.ibm.com> (raw)
In-Reply-To: <4423A391.4000301@yahoo.com.au>
On Fri, Mar 24, 2006 at 06:45:21PM +1100, Nick Piggin wrote:
> Yeah I think what's happening is that the sched groups structures
> are not shared between nodes. (It's been a while since I looked at
> this code, and it is a bit tricky to follow).
Its really odd that sched group structure aren't shared between nodes in some
case (sched_group_nodes) and are shared in other cases (sched_group_cpus,
sched_group_core, sched_group_phys).
Also is the GFP_ATOMIC allocation really required (for
sched_group_nodes) in build_sched_domains()?
--
Regards,
vatsa
next prev parent reply other threads:[~2006-03-25 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 2:58 Question on build_sched_domains Srivatsa Vaddagiri
2006-03-24 7:12 ` Srivatsa Vaddagiri
2006-03-24 7:45 ` Nick Piggin
2006-03-25 8:36 ` Srivatsa Vaddagiri [this message]
2006-03-26 2:21 ` Nick Piggin
2006-03-26 2:41 ` Srivatsa Vaddagiri
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=20060325083619.GC17011@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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