linux-kernel - Re: [PATCHSET] percpu: generalize first chunk allocators and improve lpage NUMA support

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 01 Jul 2009 08:20:38 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Christoph Lameter <cl@...ux-foundation.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.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

Hello, Christoph.

Christoph Lameter wrote:
> I looked at allocating for online cpus only a couple of years back but at
> that per cpu state was kept for offlined cpus in per cpu areas. There are
> numerous assumptions in per cpu handling all over the kernel that a percpu
> area is always available.

The plan is to allocate and keep percpu areas for cpus which have ever
been up.  There'll be no taking down of percpu areas.  Conversion from
possible to has_ever_been_up should be much easier than possible ->
online.  State keeping will work fine too.

> We successfully restricted it to only possible
> cpus. ACPI may be the worst offender there. If you can get all of that
> addressed then we can move to pure on demand allocation. Which also would
> complicate a per cpu memory allocator allocator.

I don't think it will be too complex.  The necessary bits are already
there and they are necessary for other stuff too, so...

Thanks.

-- 
tejun
--
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/