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: <20071115.140305.137877909.davem@davemloft.net>
Date:	Thu, 15 Nov 2007 14:03:05 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	clameter@....com
Cc:	corbet@....net, andi@...stfloor.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, dada1@...mosbay.com,
	schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

From: Christoph Lameter <clameter@....com>
Date: Thu, 15 Nov 2007 10:49:37 -0800 (PST)

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

Well, the first version of the patch set, the one I tested, did
require a lot of BSS space.  And that's the one they are writing
about.

I don't see how you can even remotely claim that LWN's reporting is
inaccurate here.
-
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/