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

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

Message-ID: <Pine.LNX.4.64.0711151045060.28051@schroedinger.engr.sgi.com>
Date:	Thu, 15 Nov 2007 10:49:37 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Jonathan Corbet <corbet@....net>
cc:	andi@...stfloor.org, David Miller <davem@...emloft.net>,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	dada1@...mosbay.com, schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

Well there is an LWN article now that also claims that the cpu_alloc 
patchset requires a large bss space. Sigh. See

http://lwn.net/Articles/257828/

Not true! 44 bytes is reasonable.

christoph@...pp:~/linux-2.6$ size mm/cpu_alloc.o
   text    data     bss     dec     hex filename
   5625      36      44    5705    1649 mm/cpu_alloc.o

Need to separate out the virtualization into a separate patch in V2 to 
make clear that it is there.


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