From: "Jan Beulich" <JBeulich@novell.com>
To: "Tejun Heo" <TeHeo@novell.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids
Date: Fri, 29 May 2009 07:26:55 +0100 [thread overview]
Message-ID: <4A1F9C4F020000780000337B@vpn.id2.novell.com> (raw)
In-Reply-To: <4A1F2E6E.6030105@novell.com>
>>> Tejun Heo <teheo@novell.com> 29.05.09 02:38 >>>
>There's other related larger issue. It looks like possible but
>offline configuration can be quite common with virtualization and
>allocating for all possible cpus on boot can waste problematic amount
>of space, so the plan is to allocate only for online cpus on boot and
>allocate the rest as cpus come online. This will require audit of
>percpu users and probably a new cpumask representing cpus which have
>ever been up.
>
>The issue you're describing should be solved when the above is
>implemented, right?
Yes, I think so.
Jan
prev parent reply other threads:[~2009-05-29 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 14:21 Jan Beulich
2009-05-29 0:38 ` Tejun Heo
2009-05-29 6:26 ` Jan Beulich [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=4A1F9C4F020000780000337B@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=TeHeo@novell.com \
--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
all inboxes | Powered by JetHome®