From: Gautham R Shenoy <ego@in.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, travis@sgi.com,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 1/7] work_on_cpu: helper for doing task on a CPU.
Date: Thu, 23 Oct 2008 20:06:05 +0530 [thread overview]
Message-ID: <20081023143605.GN5255@in.ibm.com> (raw)
In-Reply-To: <20081023094036.GA7593@redhat.com>
On Thu, Oct 23, 2008 at 11:40:36AM +0200, Oleg Nesterov wrote:
> On 10/23, Rusty Russell wrote:
> >
> > +long work_on_cpu(unsigned int cpu, long (*fn)(void *), void *arg)
> > +{
> > + struct work_for_cpu wfc;
> > +
> > + INIT_WORK(&wfc.work, do_work_for_cpu);
> > + init_completion(&wfc.done);
> > + wfc.fn = fn;
> > + wfc.arg = arg;
> > + get_online_cpus();
> > + if (unlikely(!cpu_online(cpu))) {
> > + wfc.ret = -EINVAL;
> > + complete(&wfc.done);
> > + } else
> > + schedule_work_on(cpu, &wfc.work);
>
> I do not claim this is wrong, but imho the code is a bit lisleading and
> needs a comment (or the "fix", please see below).
>
> Once we drop cpu_hotplug lock, CPU can go away and this work can migrate
> to another cpu.
True.
>
> > + put_online_cpus();
> > + wait_for_completion(&wfc.done);
>
> Actually you don't need work_for_cpu->done, you can use flush_work().
>
> IOW, I'd suggest
>
> long work_on_cpu(unsigned int cpu, long (*fn)(void *), void *arg)
> {
> struct work_for_cpu wfc;
>
> INIT_WORK(&wfc.work, do_work_for_cpu);
> wfc.fn = fn;
> wfc.arg = arg;
> wfc.ret = -EINVAL;
>
> get_online_cpus();
> if (likely(cpu_online(cpu))) {
> schedule_work_on(cpu, &wfc.work);
> flush_work(&wfc.work);
> }
OK, how about doing the following? That will solve the problem
of deadlock you pointed out in patch 6.
get_online_cpus();
if (likely(per_cpu(cpu_state, cpuid) == CPU_ONLINE)) {
schedule_work_on(cpu, &wfc.work);
flush_work(&wfc.work);
} else if (per_cpu(cpu_state, cpuid) != CPU_DEAD)) {
/*
* We're the CPU-Hotplug thread. Call the
* function synchronously so that we don't
* deadlock with any pending work-item blocked
* on get_online_cpus()
*/
cpumask_t orignal_mask = current->cpus_allowed;
set_cpus_allowed_ptr(current, &cpumask_of_cpu(cpu);
wfc.ret = fn(arg);
set_cpus_allowed_ptr(current, &original_mask);
}
> put_online_cpus();
>
> return wfc.ret;
> }
>
> Oleg.
>
--
Thanks and Regards
gautham
next prev parent reply other threads:[~2008-10-23 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 16:55 [PATCH 1/7] work_on_cpu: helper for doing task on a CPU Rusty Russell
2008-10-23 7:22 ` Gautham R Shenoy
2008-10-23 9:40 ` Oleg Nesterov
2008-10-23 14:36 ` Gautham R Shenoy [this message]
2008-10-23 16:35 ` Oleg Nesterov
2008-10-23 17:02 ` do_boot_cpu can deadlock? Oleg Nesterov
2008-10-23 18:21 ` Gautham R Shenoy
2008-10-23 18:49 ` Cyrill Gorcunov
2008-10-24 9:33 ` Oleg Nesterov
2008-10-24 9:53 ` Gautham R Shenoy
2008-10-24 10:51 ` Oleg Nesterov
2008-10-24 3:04 ` [PATCH 1/7] work_on_cpu: helper for doing task on a CPU Rusty Russell
2008-10-24 7:21 ` Gautham R Shenoy
2008-10-24 10:29 ` Oleg Nesterov
2008-10-24 11:18 ` Rusty Russell
2008-10-24 11:40 ` Gautham R Shenoy
2008-10-24 13:25 ` Oleg Nesterov
2008-10-24 13:41 ` Gautham R Shenoy
2008-10-24 14:23 ` Oleg Nesterov
2008-10-23 15:10 ` 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=20081023143605.GN5255@in.ibm.com \
--to=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.