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]

Date:	Tue, 13 Nov 2007 14:02:17 -0800 (PST)
From:	Christoph Lameter <clameter@....com>
To:	Eric Dumazet <dada1@...mosbay.com>
cc:	David Miller <davem@...emloft.net>, akpm@...ux-foundation.org,
	linux-mm@...r.kernel.org, linux-kernel@...r.kernel.org,
	schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

On Tue, 13 Nov 2007, Eric Dumazet wrote:

> This is because NR_CPUS is defaulted to 32 on i386 (with a limit of 256), so
> reserving 256*256KB = 64 MB of virtual space might be too much. (this is half
> the typical vmalloc area)

It defaults to 8 except if you use a NUMA system.

config NR_CPUS
        int "Maximum number of CPUs (2-255)"
        range 2 255
        depends on SMP
        default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
        default "8"

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