From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: nickpiggin@yahoo.com.au
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Question on build_sched_domains
Date: Fri, 24 Mar 2006 08:28:34 +0530 [thread overview]
Message-ID: <20060324025834.GD8903@in.ibm.com> (raw)
Nick,
I was going thr' build_sched_domains and had a question
regarding formation of sched_groups for NUMA nodes. There are two 'for'
loops, each loop possibly allocating memory (sched_group) for one or more nodes.
My question is: in the outer loop, don't we need to skip allocating for
nodes for whom the inner loop has allocated in an earlier pass?
Taking the example of 4 node system which are in the same
sched_domain_node_span(), I see that we end up allocating 16
times (when 4 would have sufficed?).
What am I missing here?
--
Regards,
vatsa
next reply other threads:[~2006-03-24 2:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 2:58 Srivatsa Vaddagiri [this message]
2006-03-24 7:12 ` Question on build_sched_domains Srivatsa Vaddagiri
2006-03-24 7:45 ` Nick Piggin
2006-03-25 8:36 ` Srivatsa Vaddagiri
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=20060324025834.GD8903@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