linux-kernel - Re: New filesystem for Linux

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 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:	Sat, 04 Nov 2006 20:07:22 +0100
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

Mikulas Patocka a écrit :
>> The problem with a per_cpu biglock is that you may consume a lot of 
>> RAM for big NR_CPUS. Count 32 KB per 'biglock' if NR_CPUS=1024
> 
> Does one Linux kernel run on system with 1024 cpus? I guess it must fry 
> spinlocks... (or even lockup due to spinlock livelocks)

Not here in my house, but I was told such beasts exist somewhere on this planet :)

You can have a kernel compiled with NR_CPUS=1024, but still run it on your 
laptop, with a single CPU available...

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