From: Roland Dreier <roland@topspin.com>
To: Timothy Miller <miller@techsource.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH - InfiniBand Access Layer (IBAL)
Date: 25 Feb 2004 09:34:21 -0800 [thread overview]
Message-ID: <52k72bjc6a.fsf@topspin.com> (raw)
In-Reply-To: <403CCC77.6030405@techsource.com>
Timothy> On the other hand, if something else is better or
Timothy> adequate, like PCI Express (wasn't that based in
Timothy> infiniband?), then there's no point.
PCI Express is not an InfiniBand replacement. While it is true (I
think this is what you meant) that the PCI Express electrical
signaling is based on InfiniBand (they both use multiple lanes of 2.5
Gb/sec high-speed serial), the upper layers of the two standards are
quite different. PCI Express and InfiniBand are really quite
complementary. In fact (just to plug my employer :) we have
demonstrated an Infiniband host adapter that has two 4X IB (10 Gb/sec
ports) and plugs into an 8X PCI Express slot:
http://www.topspin.com/news/pressrelease/pr_021704b.html
PCI Express (once products ship) will be essentially a faster PCI-X
replacement. You will get a system with PCI Express slots and plug
PCI Express adapter cards into them. There is something called PCI
Express "Advanced Switching" but that is quite a long way away from
being something you could build a cluster with.
InfiniBand on the other hand has evolved into a cluster interconnect.
In the beginning it was pitched as a PCI replacement but that was
given up long ago. However, it evolved into an excellent cluster
interconnect. Right now you can buy 10 Gb/sec host adapters and a
variety of switches (up to 96 ports). There are a number of quite
large IB clusters already built and in production already.
Best,
Roland
next prev parent reply other threads:[~2004-02-25 17:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 19:29 PATCH - InfiniBand Access Layer (IBAL) Woodruff, Robert J
2004-02-24 19:44 ` Greg KH
2004-02-24 19:50 ` Christoph Hellwig
2004-02-24 19:57 ` Greg KH
2004-02-24 22:29 ` Rik van Riel
2004-02-25 0:28 ` Matti Aarnio
2004-02-25 3:39 ` Rik van Riel
2004-02-25 16:25 ` Timothy Miller
2004-02-25 17:34 ` Roland Dreier [this message]
2004-02-25 18:55 ` Sam Ravnborg
2004-02-25 18:05 ` Linus Torvalds
2004-02-25 19:09 ` Timothy Miller
2004-02-25 19:55 ` Sam Ravnborg
2004-02-25 19:05 ` Linus Torvalds
2004-02-25 13:19 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 21:33 Woodruff, Robert J
2004-02-24 22:18 Woodruff, Robert J
2004-02-24 23:02 Woodruff, Robert J
2004-02-25 3:32 ` Rik van Riel
2004-03-13 22:07 Woodruff, Robert J
2004-03-14 1:13 ` Andrew Morton
2004-03-14 2:28 ` Greg KH
2004-03-14 3:46 Woodruff, Robert J
2004-03-15 2:10 ` Greg KH
2004-03-14 23:14 Nivedita Singhvi
2004-03-15 22:52 Woodruff, Robert J
2004-03-15 23:17 ` Christoph Hellwig
2004-03-15 23:44 ` Johannes Erdfelt
2004-03-15 23:48 ` Christoph Hellwig
2004-03-15 23:54 ` Johannes Erdfelt
2004-03-16 0:09 ` Christoph Hellwig
2004-03-16 0:18 ` Johannes Erdfelt
2004-03-16 1:41 ` Roland Dreier
2004-03-19 18:47 ` Ulrich Drepper
2004-03-19 19:21 ` Fab Tillier
2004-03-19 20:20 ` Ulrich Drepper
2004-03-19 20:47 ` Roland Dreier
2004-03-20 17:15 Acker, Dave
2004-03-20 17:55 ` Ulrich Drepper
2004-03-21 22:16 ` Roland Dreier
2004-03-20 19:15 Acker, Dave
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=52k72bjc6a.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.