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: <12c511ca0705020954q1230ae85o9ab7ca609fd07507@mail.gmail.com>
Date:	Wed, 2 May 2007 09:54:04 -0700
From:	"Tony Luck" <tony.luck@...el.com>
To:	"Daniel J Blueman" <daniel.blueman@...il.com>
Cc:	"Rajib Majumder" <rajibm2005@...il.com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: Kernel Scalability

On 5/2/07, Daniel J Blueman <daniel.blueman@...il.com> wrote:
>
> There are 128-processor IA64 systems which run recent 2.6 kernels out
> there; the per-processor counters, RCU and page-fault scalability work
> has been instrumental to the necessary scaling for decent resource
> usage on these.

128 cpu is a bit dated ... there are 512 and 1024 cpu systems being
used in production environments.  The highest reported count stands
at 4096 ... but that was only a prototype system, not a production
machine ... a small number of patches were needed to boot (e.g.
with 10 kernel daemons per cpu, a default kernel hits the maximum
number of process ids limit!).

The question of how well it scales is very workload dependent.  Most
of those high cpu count systems are running scientific workloads that
crunch numbers in user mode for 7.5 million years before making a
single syscall to print that the answer is 42. Obviously scaling of
such applications is near linear.

But your original question was about 4-8 cpus with 2.4/2.6 ... you
will almost certainly be a lot happier with a recent 2.6 kernel. A
great deal of work has been done to make it scale well.  But
there are still some dark corners that haven't been cleaned up
so you will have to run your target application and make your
own measurments on scaling.  If you find that it doesn't scale
well, then we'd like to hear about it here.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ