linux-kernel - Re: [patch 01/28] cpu alloc: The allocator

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 Nov 2007 18:03:51 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	David Miller <davem@...emloft.net>
cc:	andi@...stfloor.org, akpm@...ux-foundation.org,
	linux-mm@...r.kernel.org, linux-kernel@...r.kernel.org,
	dada1@...mosbay.com, schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

On Tue, 13 Nov 2007, David Miller wrote:

> From: Christoph Lameter <clameter@....com>
> Date: Tue, 13 Nov 2007 17:57:15 -0800 (PST)
> 
> > Hmmmm. cpu_alloc really does not need zeroed data. Just an address
> > fixed by the compiler where stuff can be put. Can the loader do that
> > somehow?
> 
> Yes, and I think IA64 uses such a scheme for it's 64KB fixed
> per-cpu TLB mapping thing doesn't it?

The per cpu TLB mapping is virtually mapped. The real memory allocation 
behind it occurs dynamically from bootmem.

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