linux-kernel - Re: percpu memory setup and num_possible_cpus() vs. nr_cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <4A1F9C4F020000780000337B@vpn.id2.novell.com>
Date:	Fri, 29 May 2009 07:26:55 +0100
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Tejun Heo" <TeHeo@...ell.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: percpu memory setup and num_possible_cpus() vs. nr_cpu_ids

>>> Tejun Heo <teheo@...ell.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/