[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090701063455.GL6760@one.firstfloor.org>
Date: Wed, 1 Jul 2009 08:34:55 +0200
From: Andi Kleen <andi@...stfloor.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: Christoph Lameter <cl@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>, tj@...nel.org,
linux-kernel@...r.kernel.org, x86@...nel.org,
linux-arch@...r.kernel.org, andi@...stfloor.org, hpa@...or.com,
tglx@...utronix.de
Subject: Re: [PATCHSET] percpu: generalize first chunk allocators and improve lpage NUMA support
> Say it says "256 CPUs".
>
> But i only run a 2 CPU guest system. But i want to run it with the
> _on demand capability_ to scale up to 256 virtual CPUs if needed,
> without having to reboot the guest and without having to allocate
> all the percpu space for 256 CPUs beforehand. Ok?
Then you would need to fix lots of subsystems. Everyone doing
for_each_possible_cpu() today and not having a cpu notifier callback.
git/linux-2.6% gid for_each_possible_cpu | wc -l
247
git/linux-2.6% gid CPU_UP_PREPARE | wc -l
48
Essentially you would discard the concept of possible CPUs
and replace it only with online CPUs, but possible CPUs
are widely used.
It's unclear to me it's worth all that work (and how to test
it properly), assuming we fix the few per cpu pigs today that make it
very expensive to preallocate percpu in the big debug configurations.
> It is a simple, basic OS feature and concept.
.. that Linux doesn't support without some heavy lifting.
Not answering emails will not change that fact.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
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/
Powered by blists - more mailing lists