From: Tejun Heo <tj@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Laurent Vivier <lvivier@redhat.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/workqueue: update list of possible CPUs
Date: Wed, 23 Aug 2017 06:26:42 -0700 [thread overview]
Message-ID: <20170823132642.GH491396@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <87lgmay2eg.fsf@concordia.ellerman.id.au>
Hello, Michael.
On Wed, Aug 23, 2017 at 09:00:39PM +1000, Michael Ellerman wrote:
> > I don't think that's true. The CPU id used in kernel doesn't have to
> > match the physical one and arch code should be able to pre-map CPU IDs
> > to nodes and use the matching one when hotplugging CPUs. I'm not
> > saying that's the best way to solve the problem tho.
>
> We already virtualise the CPU numbers, but not the node IDs. And it's
> the node IDs that are really the problem.
Yeah, it just needs to match up new cpus to the cpu ids assigned to
the right node.
> > It could be that the best way forward is making cpu <-> node mapping
> > dynamic and properly synchronized.
>
> We don't need it to be dynamic (at least for this bug).
The node mapping for that cpu id changes *dynamically* while the
system is running and that can race with node-affinity sensitive
operations such as memory allocations.
> Laurent is booting Qemu with a fixed CPU <-> Node mapping, it's just
> that because some CPUs aren't present at boot we don't know what the
> node mapping is. (Correct me if I'm wrong Laurent).
>
> So all we need is:
> - the workqueue code to cope with CPUs that are possible but not online
> having NUMA_NO_NODE to begin with.
> - a way to update the workqueue cpumask when the CPU comes online.
>
> Which seems reasonable to me?
Please take a step back and think through the problem again. You
can't bandaid it this way.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-08-23 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 13:49 [PATCH 1/2] powerpc/workqueue: update list of possible CPUs Laurent Vivier
2017-08-21 13:49 ` [PATCH 2/2] blk-mq: don't use WORK_CPU_UNBOUND Laurent Vivier
2017-08-21 14:48 ` Tejun Heo
2017-08-21 14:48 ` [PATCH 1/2] powerpc/workqueue: update list of possible CPUs Tejun Heo
2017-08-22 1:41 ` Michael Ellerman
2017-08-22 16:54 ` Tejun Heo
2017-08-23 11:00 ` Michael Ellerman
2017-08-23 11:17 ` Laurent Vivier
2017-08-23 13:26 ` Tejun Heo [this message]
2017-08-24 12:10 ` Laurent Vivier
2017-08-24 13:51 ` Tejun Heo
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=20170823132642.GH491396@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=axboe@kernel.dk \
--cc=jiangshanlai@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=mpe@ellerman.id.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 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.