From: Nathan Lynch <ntl@pobox.com>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Tony Luck <tony.luck@intel.com>,
linux-kernel@vger.kernel.org, Ben Collins <bcollins@debian.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] fix workqueue oops during cpu offline
Date: Thu, 5 Jan 2006 17:18:06 -0600 [thread overview]
Message-ID: <20060105231806.GF16729@localhost.localdomain> (raw)
In-Reply-To: <20060105144210.A14956@unix-os.sc.intel.com>
Ashok Raj wrote:
> On Thu, Jan 05, 2006 at 01:45:50PM -0800, Tony Luck wrote:
> > On 1/4/06, Nathan Lynch <ntl@pobox.com> wrote:
> > > This is where things go wrong -- any_online_cpu() now gets 1, not 0.
> > > In queue_work, the cpu_workqueue_struct at per_cpu_ptr(wq->cpu_wq, 1) is
> > > uninitialized.
> >
> > Same issue on ia64 when I tried to add Ashok' s patch to allow
> > removal of cpu0 (BSP in ia64-speak). Ashok told me that this fix
> > solves the problem for us too.
> >
>
> Is this safe to use in NUMA path as well? Not that memory hot-remove is there
> yet today, but if a NUMA node is being removed, i would assume the memory for
> that node goes with it. i.e assuming alloc_percpu() gets node local memory for
> each cpu.
I guess I don't understand your concern here -- the workqueue patch
doesn't introduce any potential difficulty with memory or node removal
that alloc_percpu didn't already have.
> So is it safe to continue to reference an area of an offline cpu that may not
> exist?
Yes.
prev parent reply other threads:[~2006-01-05 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 4:58 [PATCH] fix workqueue oops during cpu offline Nathan Lynch
2006-01-05 5:58 ` Nigel Cunningham
2006-01-05 6:03 ` Benjamin Herrenschmidt
2006-01-05 14:30 ` Ben Collins
2006-01-05 21:45 ` Tony Luck
2006-01-05 22:42 ` Ashok Raj
2006-01-05 23:18 ` Nathan Lynch [this message]
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=20060105231806.GF16729@localhost.localdomain \
--to=ntl@pobox.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox