From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Pekka Pietikainen <pp@evil.netppl.fi>
Cc: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Dolphin PCI-SCI RPM Drivers 1.1-4 released
Date: Tue, 30 Jan 2001 20:18:18 +0200 [thread overview]
Message-ID: <20010130201818.X25659@mea-ext.zmailer.org> (raw)
In-Reply-To: <20010129164953.A15219@vger.timpanogas.org> <Pine.A41.4.31.0101292123270.54650-100000@aix06.unm.edu> <20010130101958.A18047@vger.timpanogas.org> <20010130192248.A3684@netppl.fi>
In-Reply-To: <20010130192248.A3684@netppl.fi>; from pp@evil.netppl.fi on Tue, Jan 30, 2001 at 07:22:48PM +0200
On Tue, Jan 30, 2001 at 07:22:48PM +0200, Pekka Pietikainen wrote:
> On Tue, Jan 30, 2001 at 10:19:58AM -0700, Jeff V. Merkey wrote:
> > On Mon, Jan 29, 2001 at 09:41:21PM -0700, Todd wrote:
> >
> > Sparc servers. The adapters these drivers I posted support are a bi-CMOS
> > implementation of the SCI LC3 chipsets, and even though they are
> > bi-CMOS, the Link speed on the back end is still 500 MB/S --
> > very respectable.
> Sounds impressive (and expensive)
Impressive yes, expensive ? Everything is relative.
Well, you can propably buy a truck-load of cheap 100BaseT cards
with the price of Sun UPA connected SCI interface, but there is
no point at connecting SCI anywhere but into the system core bus.
PCI is "mediocre speed" IO-bus, never forget that.
(But there is nothing better yet! 66+MHz 64bit PCI-X gives some
hope for faster IO-busses, but is still quite inadequate..)
People who want to use SCI have serious nonccNUMA PVM programs
(Beowulf-like) where interconnect message latency may well be
the difference in between a successfull system, and failure.
(Even when all optimization is pushed into extreme and as little,
and infrequent interconnect messages are needed as possible with
given problem. Reminds me of solving partial differential equations
via FFT method in parallel system -- interconnect memory access speeds
ruled the result. Nothing beats Cray T3E there yet.)
Giga-Ethernet has 9.9 Gbit/sec mode, as well as something close
to 40 Gbit/sec. Those may yet be superior interconnects - or
maybe not. Throwing around Ethernet frames is non-trivial task
compared to SCI. But what may yet emerge are chipsets and system
busses able to sustain that kind of traffics, and optimize operation
for SCI. 40GE uses bits serial optical transmission at 40+ GHz ...
(E.g. 18/16 encoded codewords, or some such. FE uses 5/4 encoding,
if I remember correctly.)
> --
> Pekka Pietikainen
/Matti Aarnio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 18:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-29 21:27 Jeff V. Merkey
2001-01-29 23:49 ` Jeff V. Merkey
2001-01-30 4:41 ` Todd
2001-01-30 17:19 ` Jeff V. Merkey
2001-01-30 17:07 ` Todd
2001-01-30 18:07 ` Jeff V. Merkey
2001-01-30 17:22 ` Pekka Pietikainen
2001-01-30 18:18 ` Matti Aarnio [this message]
2001-01-30 19:01 ` Jeff V. Merkey
2001-01-30 17:32 ` Jeff V. Merkey
2001-01-30 17:11 ` Todd
2001-01-30 17:49 ` Jeff V. Merkey
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=20010130201818.X25659@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pp@evil.netppl.fi \
/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
all inboxes | Powered by JetHome®