From: "Greg Chesson" <greg@xtp.engr.sgi.com>
To: alan@lxorguk.ukuu.org.uk (Alan Cox), ariel@cthulhu.engr.sgi.com
Cc: galibert@pobox.com, linux@cthulhu.engr.sgi.com
Subject: Re: help offered
Date: Wed, 25 Nov 1998 13:04:47 -0800 [thread overview]
Message-ID: <9811251304.ZM24036@xtp.engr.sgi.com> (raw)
In-Reply-To: alan@lxorguk.ukuu.org.uk (Alan Cox) "Re: help offered" (Nov 25, 9:46pm)
One definition of OS scalability that I have not seen
in general use is this:
an OS scales to S number of processors if all S processors
can be executing in the kernel at the same time.
An OS that scales to S active kernels can usually operate hardware
with P processors, where P > S. A system for 1P should
be able to handle 2P with a little work. I expect a lightweight kernel
like Linux to handle 4p with a few locks if on average only one of the
4p is in the kernel. I'd suggest that the LInux kernel is at present
(1S, 4p) or maybe (1.5S, 4P).
g
--
Greg Chesson
WARNING: multiple messages have this Message-ID (diff)
From: "Greg Chesson" <greg@xtp.engr.sgi.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, ariel@cthulhu.engr.sgi.com
Cc: galibert@pobox.com, linux@cthulhu.engr.sgi.com
Subject: Re: help offered
Date: Wed, 25 Nov 1998 13:04:47 -0800 [thread overview]
Message-ID: <9811251304.ZM24036@xtp.engr.sgi.com> (raw)
Message-ID: <19981125210447.P4LV2db7m9aWacWK-soBrI70mYrpEMPwXCcUqwDhJXo@z> (raw)
In-Reply-To: alan@lxorguk.ukuu.org.uk (Alan Cox) "Re: help offered" (Nov 25, 9:46pm)
One definition of OS scalability that I have not seen
in general use is this:
an OS scales to S number of processors if all S processors
can be executing in the kernel at the same time.
An OS that scales to S active kernels can usually operate hardware
with P processors, where P > S. A system for 1P should
be able to handle 2P with a little work. I expect a lightweight kernel
like Linux to handle 4p with a few locks if on average only one of the
4p is in the kernel. I'd suggest that the LInux kernel is at present
(1S, 4p) or maybe (1.5S, 4P).
g
--
Greg Chesson
next prev parent reply other threads:[~1998-11-25 21:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-24 12:27 help offered Torbjörn Gannholm
1998-11-24 20:33 ` Ariel Faigon
1998-11-25 19:49 ` Olivier Galibert
1998-11-25 19:57 ` John E. Schimmel
1998-11-25 19:57 ` John E. Schimmel
1998-11-25 20:11 ` Jeffrey Watts
1998-11-25 20:43 ` Greg Chesson
1998-11-25 20:37 ` Ariel Faigon
1998-11-25 20:37 ` Ariel Faigon
1998-11-25 20:51 ` pjlahaie
1998-11-25 21:18 ` William J. Earl
1998-11-25 21:18 ` William J. Earl
1998-11-25 21:24 ` Greg Chesson
1998-11-25 21:24 ` Greg Chesson
1998-11-25 21:38 ` pjlahaie
1998-11-25 21:57 ` Greg Chesson
1998-11-25 21:57 ` Greg Chesson
1998-11-25 22:09 ` pjlahaie
1998-11-25 22:57 ` Greg Chesson
1998-11-25 22:57 ` Greg Chesson
1998-11-25 22:08 ` William J. Earl
1998-11-25 22:08 ` William J. Earl
1998-11-25 22:13 ` Alex Kozlov
1998-11-25 22:15 ` pjlahaie
1998-11-25 22:25 ` William J. Earl
1998-11-25 22:25 ` William J. Earl
1998-11-25 21:46 ` Alan Cox
1998-11-25 21:04 ` Greg Chesson [this message]
1998-11-25 21:04 ` Greg Chesson
1998-11-26 12:28 ` ralf
[not found] ` <19981126085407.A2201@uni-koblenz.de>
1998-11-27 22:59 ` Olivier Galibert
1998-11-28 2:45 ` ralf
1998-11-26 22:17 ` Miguel de Icaza
1998-11-25 20:56 ` Greg Chesson
1998-11-25 21:12 ` Olivier Galibert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9811251304.ZM24036@xtp.engr.sgi.com \
--to=greg@xtp.engr.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ariel@cthulhu.engr.sgi.com \
--cc=galibert@pobox.com \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox