From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: galibert@pobox.com (Olivier Galibert)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: help offered
Date: Wed, 25 Nov 1998 12:37:36 -0800 (PST) [thread overview]
Message-ID: <199811252037.MAA37649@oz.engr.sgi.com> (raw)
In-Reply-To: <19981125204900.A4692@loria.fr> from "Olivier Galibert" at Nov 25, 98 08:49:00 pm
:
:> - Guaranteed Real Time response (kernel is preemptible
:> i.e. you can have multiple system calls executing in server
:> space simultaneously.
:
:Linux 2.1.* is very preemtible, even if there are stil some things to
:do.
:
Interesting. Could you elaborate on:
0) What was changed in recent Linux kernels
to support preemtibility in kernel space?
1) Which "serious" (i.e not 'getpid') system calls are
now reentrant ?
2) What still remains to be done so Linux can really
scale before it gets bottlenecked by kernel locks ?
:> - Bandwidth (I/O networking) e.g. 4 GB/sec write to
:> RAID disks.
:
:Interesting. Our "local" SGI vendor (i.e. the one for France), told
:us that 1GB/sec write speed was too much and he could only guarantee
:800MB/sec for our 1TB raid array.
:
I've seen way much higher numbers. They are not official, and
are not supposed to be used in sales situations, but were obtained
in our labs with XFS and arrays that were designed and tuned to
maximize bandwidth and to prove that XFS is not the bottleneck.
I believe they also used fiberchannel etc. Anyway, there are
some much greater experts on this subject on this list if they
care to give the details.
:
:> Note that Linux doesn't even support big files (more than 4 GB)
:> on x86, while IRIX supports many terabyte files.
:
:The limit on x86 is 2GB. To be fair, said terabyte files and
:filesystems are connected to systems with a 64bits architecture.
:Afaik, linux on alpha handles terabytes files.
:
Yes, I know this is not a strictly-Linux limitation, which is why
I was careful to add "on x86".
Please don't get me wrong: I'm not trying to advocate any OS over
the other (I love and use both) and I didn't mean to turn this
into an advocacy thread. I was just to respond honestly and fairly
to a specific question I was asked.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: Olivier Galibert <galibert@pobox.com>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: help offered
Date: Wed, 25 Nov 1998 12:37:36 -0800 (PST) [thread overview]
Message-ID: <199811252037.MAA37649@oz.engr.sgi.com> (raw)
Message-ID: <19981125203736.mGhZ5KeSmm_w12-ikHwvBCDjeCLXGc5-Jmnu6X3z5ek@z> (raw)
In-Reply-To: <19981125204900.A4692@loria.fr> from "Olivier Galibert" at Nov 25, 98 08:49:00 pm
:
:> - Guaranteed Real Time response (kernel is preemptible
:> i.e. you can have multiple system calls executing in server
:> space simultaneously.
:
:Linux 2.1.* is very preemtible, even if there are stil some things to
:do.
:
Interesting. Could you elaborate on:
0) What was changed in recent Linux kernels
to support preemtibility in kernel space?
1) Which "serious" (i.e not 'getpid') system calls are
now reentrant ?
2) What still remains to be done so Linux can really
scale before it gets bottlenecked by kernel locks ?
:> - Bandwidth (I/O networking) e.g. 4 GB/sec write to
:> RAID disks.
:
:Interesting. Our "local" SGI vendor (i.e. the one for France), told
:us that 1GB/sec write speed was too much and he could only guarantee
:800MB/sec for our 1TB raid array.
:
I've seen way much higher numbers. They are not official, and
are not supposed to be used in sales situations, but were obtained
in our labs with XFS and arrays that were designed and tuned to
maximize bandwidth and to prove that XFS is not the bottleneck.
I believe they also used fiberchannel etc. Anyway, there are
some much greater experts on this subject on this list if they
care to give the details.
:
:> Note that Linux doesn't even support big files (more than 4 GB)
:> on x86, while IRIX supports many terabyte files.
:
:The limit on x86 is 2GB. To be fair, said terabyte files and
:filesystems are connected to systems with a 64bits architecture.
:Afaik, linux on alpha handles terabytes files.
:
Yes, I know this is not a strictly-Linux limitation, which is why
I was careful to add "on x86".
Please don't get me wrong: I'm not trying to advocate any OS over
the other (I love and use both) and I didn't mean to turn this
into an advocacy thread. I was just to respond honestly and fairly
to a specific question I was asked.
--
Peace, Ariel
next prev parent reply other threads:[~1998-11-25 20:38 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 [this message]
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
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=199811252037.MAA37649@oz.engr.sgi.com \
--to=ariel@oz.engr.sgi.com \
--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