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.0711132023290.7631@schroedinger.engr.sgi.com>
Date:	Tue, 13 Nov 2007 20:26:33 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	David Miller <davem@...emloft.net>
cc:	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

On Tue, 13 Nov 2007, David Miller wrote:

> From: Christoph Lameter <clameter@....com>
> Date: Tue, 13 Nov 2007 20:15:55 -0800 (PST)
> 
> > Guess I need also to add an arch configuration guide to V2 as well so that 
> > the other arches can do similar tricks and emphasize that the static 
> > default that requires bss is only suitable for small systems.
> 
> I'm going to be against your changes until you implement
> a real fix for the BSS bloat problems.
> 
> It's worse than the per-cpu allocator we have now, much
> worse.

You need to configure cpu_alloc for your arch and so far you seem 
to not have had the time to understand how it works otherwise you would 
not repeat these statements and ask me to implement what the 
patch already provides.

The only problem that I see so far is a communication problem. Thus we 
need more documentation.
-
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/