From: "M.Baris Demiray" <baris@labristeknoloji.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Andrew Morton <akpm@osdl.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.12-rc6-mm1] add allowed CPUs check into find_idlest_{group|cpu}()
Date: Wed, 08 Jun 2005 21:07:38 +0000 [thread overview]
Message-ID: <42A75E1A.8030803@labristeknoloji.com> (raw)
In-Reply-To: <1118191744.5104.49.camel@npiggin-nld.site>
[-- Attachment #1: Type: text/plain, Size: 2369 bytes --]
Nick Piggin wrote:
> [...]
> Hi,
Hi Nick,
> [...]
>
> By taking the intersection in find_idlest_cpu, I don't mean checking
> whether or not they intersect as in find_idlest_group. I mean doing
> this:
>
>
> cpumask_t tmp;
>
> /* Find the intersection */
> cpus_and(tmp, group->cpumask, p->cpus_allowed);
>
> for_each_cpu_mask(i, tmp) {
>
> Right? That is effectively the same as what you've got in your patch,
> but it means we don't need to do the cpumask comparison every time
> around the loop (aside from being an extra branch, the actual operation
> itself gets a little costly with huge cpu masks).
You're right, I got it. Updated version is appended.
--- linux-2.6.12-rc6-mm1/kernel/sched.c.orig 2005-06-08
00:28:59.000000000 +0000
+++ linux-2.6.12-rc6-mm1/kernel/sched.c 2005-06-08 20:45:25.000000000 +0000
@@ -1039,8 +1039,11 @@
int local_group;
int i;
+ /* Loop over if group has no CPUs allowed */
+ if (!cpus_intersects(group->cpumask, p->cpus_allowed))
+ continue;
+
local_group = cpu_isset(this_cpu, group->cpumask);
- /* XXX: put a cpus allowed check */
/* Tally up the load of all CPUs in the group */
avg_load = 0;
@@ -1076,13 +1079,17 @@
/*
* find_idlest_queue - find the idlest runqueue among the cpus in group.
*/
-static int find_idlest_cpu(struct sched_group *group, int this_cpu)
+static int find_idlest_cpu(struct sched_group *group, struct
task_struct *p,
+ int this_cpu)
{
unsigned long load, min_load = ULONG_MAX;
int idlest = -1;
int i;
+ cpumask_t allowed_cpus;
- for_each_cpu_mask(i, group->cpumask) {
+ /* Traverse only the allowed CPUs */
+ cpus_and(allowed_cpus, group->cpumask, p->cpus_allowed);
+ for_each_cpu_mask(i, allowed_cpus) {
load = source_load(i, 0);
if (load < min_load || (load == min_load && i == this_cpu)) {
@@ -1124,7 +1131,7 @@
if (!group)
goto nextlevel;
- new_cpu = find_idlest_cpu(group, cpu);
+ new_cpu = find_idlest_cpu(group, t, cpu);
if (new_cpu == -1 || new_cpu == cpu)
goto nextlevel;
PS: Thanks for your help and patience :-)
> Nick
>
--
"You have to understand, most of these people are not ready to be
unplugged. And many of them are no inert, so hopelessly dependent
on the system, that they will fight to protect it."
Morpheus
[-- Attachment #2: baris.vcf --]
[-- Type: text/x-vcard, Size: 342 bytes --]
begin:vcard
fn:M.Baris Demiray
n:Demiray;M.Baris
org:Labris Teknoloji
adr:;;Teknokent Silikon Bina No:24 ODTU;Ankara;;06531;Turkey
email;internet:baris@labristeknoloji.com
title:Yazilim Gelistirme Uzmani
tel;work:+903122101490
tel;fax:+903122101492
x-mozilla-html:FALSE
url:http://www.labristeknoloji.com
version:2.1
end:vcard
next prev parent reply other threads:[~2005-06-08 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 3:22 M.Baris Demiray
2005-06-08 0:49 ` Nick Piggin
2005-06-08 21:07 ` M.Baris Demiray [this message]
2005-06-09 0:24 ` Nick Piggin
2005-06-09 10:08 ` M.Baris Demiray
2005-06-09 12:01 ` Nick Piggin
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=42A75E1A.8030803@labristeknoloji.com \
--to=baris@labristeknoloji.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®