From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "M.Baris Demiray" <baris@labristeknoloji.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2.6.12-rc5-mm2] [sched] add allowed CPUs check into find_idlest_group()
Date: Mon, 06 Jun 2005 11:44:03 +1000 [thread overview]
Message-ID: <42A3AA63.7060201@yahoo.com.au> (raw)
In-Reply-To: <42A3381F.90801@labristeknoloji.com>
M.Baris Demiray wrote:
>
> Hello,
> following patch adds check for allowed CPUs into
> sched.c:find_idlest_group() -as told in comment line that had
> removed-. But, I have several questions about that comment.
>
> Firstly, I've understood it as "Check whether process p is allowed to
> run on each CPU of to-be-found idlest group"; is that right?
>
Close.
Probably it would be better to take the intersection of
(group->cpumask, p->cpus_allowed), and skip the group if
the intersection is empty.
In addition to that, do a patch for find_idlest_cpu that
skips cpus that aren't allowed. You needn't do the cpumask
check each time round the loop, again just take the
intersection of the group->cpumask and p->cpus_allowed, and
loop over that.
Wanna do a patch for that?
> If so, isn't it more appropriate to do check in find_idlest_cpu()?
> Because, we're only interested in CPUs that are in idlest group
> but doing a check in find_idlest_group() also checks for CPUs
> that are not in idlest group (since we're traversing all the groups
> in given domain). Checking this after finding the idlest group
> (in find_idlest_cpu() with ordinary call order as in
> sched_balance_self()) will save us from extra overhead.
>
> Although I've questions in my mind, I'm sending a patch following
> that comment. Any explanation and comment on patch will be
> appreciated.
>
I don't think it does anything ;)
> Regards.
>
> Signed-off-by: M.Baris Demiray <baris@labristeknoloji.com>
>
> --- linux-2.6.12-rc5-mm2/kernel/sched.c.orig 2005-06-05
> 12:31:04.000000000 +0000
> +++ linux-2.6.12-rc5-mm2/kernel/sched.c 2005-06-05 16:49:49.000000000
> +0000
> @@ -1040,7 +1040,12 @@
> int i;
>
> local_group = cpu_isset(this_cpu, group->cpumask);
> - /* XXX: put a cpus allowed check */
> +
> + /* Check whether all CPUs in the group is allowed to run on */
> + for_each_cpu_mask(i, group->cpumask) {
> + if (!cpu_isset(i, p->cpus_allowed))
> + continue;
> + }
>
> /* Tally up the load of all CPUs in the group */
> avg_load = 0;
>
>
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-06-06 1:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 17:36 [PATCH 2.6.12-rc5-mm2] [sched] add allowed CPUs check into find_idlest_group() M.Baris Demiray
2005-06-06 1:44 ` Nick Piggin [this message]
2005-06-06 11:13 ` M.Baris Demiray
2005-06-06 10:36 ` Nick Piggin
2005-06-06 13:59 ` M.Baris Demiray
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=42A3AA63.7060201@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=baris@labristeknoloji.com \
--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