From: Rusty Russell <rusty@rustcorp.com.au>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/16] staging/lustre: fix up obsolete cpu function usage.
Date: Tue, 03 Mar 2015 10:09:07 +1030 [thread overview]
Message-ID: <87twy3j7fo.fsf@rustcorp.com.au> (raw)
In-Reply-To: <74B1B5A4-D3CE-4A7A-A09B-6B755623ADA4@linuxhacker.ru>
Oleg Drokin <green@linuxhacker.ru> writes:
> Thanks!
> Seems there was a midair collsion with my own patch that was not as comprehensive
> wrt functions touched: https://lkml.org/lkml/2015/3/2/10
Yep, I posted this for completeness (and for your reference), but
figured you'd handle it.
> But on the other hand I also tried to clean up
> some of the NR_CPUS usage while I was at it and this raises
> this question, from me, in the code like:
>
> for_each_cpu_mask(i, blah) {
> blah
> if (something)
> break;
> }
> if (i == NR_CPUS)
> blah;
>
> when we are replacing for_each_cpu_mask with for_each_cpu,
> what do we check the counter against now to see that the entire loop was executed
> and we did not exit prematurely? nr_cpu_ids?
You want >= nr_cpu_ids here.
> Also I assume we still want to get rid of direct cpumask assignments like
>> mask = *cpumask_of_node(cpu_to_node(index));
Yes, but this code is wrong anyway:
mask = *cpumask_of_node(cpu_to_node(index));
for (i = max; i < num_online_cpus(); i++)
cpumask_clear_cpu(i, &mask);
*Never* iterate to num_online_cpus(). eg. if cpus 0 and 3 are online,
num_online_cpus() == 2. I'm not sure what this code is doing, but it's
not doing it well :)
There are several issues here. You need to handle cpus going offline
(during this routine, as well as after). You need to use a
cpumask_var_t, like so:
cpumask_var_t mask;
...
case PDB_POLICY_NEIGHBOR:
if (!alloc_cpumask_var(&mask, GFP_???)) {
rc = -ENOMEM;
break;
}
...
Or get rid of the mask altogether, eg:
pc->pc_npartners = -1;
for_each_cpu(i, cpu_online_mask) {
if (i < max)
pc->pc_npartners++;
}
...
pidx = 0;
for_each_cpu(i, cpu_online_mask) {
if (i >= max)
break;
ppc = &ptlrpcds->pd_threads[i];
pc->pc_partners[pidx++] = ppc;
ppc->pc_partners[ppc->pc_npartners++] = pc;
}
[ This is off the top of my head, no idea if it's right...]
Thanks,
Rusty.
next prev parent reply other threads:[~2015-03-02 23:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 11:35 [PATCH 01/16] CONFIG_DISABLE_OBSOLETE_CPUMASK_FUNCTIONS: set if CPUMASK_OFFSTACK Rusty Russell
2015-03-02 11:35 ` [PATCH 02/16] cpumask: fix cpu-hotplug documentation Rusty Russell
2015-03-02 11:35 ` [PATCH 03/16] ia64: Use for_each_cpu_and() and cpumask_any_and() instead of temp var Rusty Russell
2015-03-02 11:35 ` [PATCH 04/16] drivers: fix up obsolete cpu function usage Rusty Russell
2015-03-02 22:23 ` Rafael J. Wysocki
2015-03-02 11:35 ` [PATCH 05/16] staging/lustre: " Rusty Russell
2015-03-02 17:50 ` Oleg Drokin
2015-03-02 23:39 ` Rusty Russell [this message]
2015-03-03 1:16 ` Oleg Drokin
2015-03-03 3:12 ` Rusty Russell
2015-03-02 11:35 ` [PATCH 06/16] ia64: " Rusty Russell
2015-05-26 20:45 ` Tony Luck
2015-05-27 1:18 ` Rusty Russell
2015-05-27 17:37 ` Tony Luck
2015-05-28 3:44 ` Rusty Russell
2015-03-02 11:35 ` [PATCH 07/16] um: " Rusty Russell
2015-03-02 11:35 ` [PATCH 08/16] x86: " Rusty Russell
2015-03-02 13:36 ` [tip:x86/cleanups] x86: Fix up obsolete __cpu_set() " tip-bot for Rusty Russell
2015-03-02 11:35 ` [PATCH 09/16] mips: fix up obsolete cpu " Rusty Russell
2015-03-02 12:34 ` [PATCH 01/16] CONFIG_DISABLE_OBSOLETE_CPUMASK_FUNCTIONS: set if CPUMASK_OFFSTACK Paul Bolle
2015-03-02 23:40 ` Rusty Russell
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=87twy3j7fo.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=green@linuxhacker.ru \
--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
Powered by JetHome