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: <20071113.173643.78069123.davem@davemloft.net>
Date:	Tue, 13 Nov 2007 17:36:43 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	clameter@....com
Cc:	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

From: Christoph Lameter <clameter@....com>
Date: Tue, 13 Nov 2007 14:20:02 -0800 (PST)

> On Tue, 13 Nov 2007, David Miller wrote:
> 
> > Yes, I could add virtualized area support to sparc64, but we cannot
> > impose this on every platform.
> 
> Other platforms do not have the 8MB restriction nor do they have so many 
> processors.

sparc32 has the same limitations, nobody is going to implement
the virt stuff there.

> Here is the draft of a virtual cpu area implementation for sparc64. Uses 
> the VMEMMAP chunks:

This doesn't avoid the core problem.  Bloating up the BSS like
that is bad, end enforcing a virt implementation to avoid that
is an anti-social way to go about implementing this feature.
-
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/