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.191711.44685807.davem@davemloft.net>
Date:	Thu, 15 Nov 2007 19:17:11 -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 19:10:15 -0800 (PST)

> On Thu, 15 Nov 2007, David Miller wrote:
> 
> > > I have not looked at sparc32 sorry. If you simply set up a couple of 
> > > configuration values in arch/sparc32/Kconfig then everything will be fine.
> > 
> > There is assembler code to write, which as I stated several
> > times nobody is going to work on or test.
> 
> There is no assembly code required. I overdid it in the patch that I sent 
> you trying to make sparc64 use large mappings like x86_64 NUMA. You really 
> do not need that. Look at the IA64 and i386 configurations. There is no C 
> code required. The x86_64 code only adds some special C code for the NUMA 
> case.

Ok, and like I said last time, I'll examine this more closely
when you spin your next version of these patches.

Please post them soon as I'm eager to test this stuff out for
you.

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