netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: jaganav@us.ibm.com
Cc: Roland Dreier <roland@topspin.com>,
	Dmitry Yusupov <dmitry_yus@yahoo.com>,
	open-iscsi@googlegroups.com,
	"David S. Miller" <davem@davemloft.net>,
	mpm@selenic.com, andrea@suse.de, michaelc@cs.wisc.edu,
	James.Bottomley@HansenPartnership.com,
	ksummit-2005-discuss@thunk.org, netdev@oss.sgi.com,
	Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: Linux support for RDMA
Date: Thu, 31 Mar 2005 17:57:22 -0800	[thread overview]
Message-ID: <424CAA82.1010707@zytor.com> (raw)
In-Reply-To: <1112320148.424ca894f3c8b@imap.linux.ibm.com>

jaganav@us.ibm.com wrote:
> 
> No doubt, Ethernet will eventually win .. btw, Hasn't history proven this over
> ATM? More specifically when the industry predicted that ATM will replace
> ethernet :)
> 
> However, I'll have to agree with Ben that IB technolgy will fill an important
> niche segment, more specifically so in the low end of High Performance Computing
> (HPC) segment which is in a transition mode currently moving away from
> proprietary interconnects to industry standards based IB technology. Eventhough,
> ethernet may eventually may catch up with IB in terms of the bandwidth but IB
> fabrics can offer better latencies.
> 

We've seen this over and over... Token Ring, FDDI, ATM, IB, ... all of 
them "better" than the Ethernet of the day, but eventually 
commoditization wins out.  With 10GE, Ethernet has finally stopped 
pretending to be CSMA/CD even; "Ethernet" is now really nothing more 
than a collective name for a set of somewhat compatible commodity 
networking technologies.

	-hpa

  reply	other threads:[~2005-04-01  1:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-01  1:49 Linux support for RDMA jaganav
2005-04-01  1:57 ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-02  1:59 jaganav
2005-04-01 23:50 Asgeir Eiriksson
2005-04-02  0:02 ` Dmitry Yusupov
     [not found] <20050324233921.GZ14202@opteron.random>
     [not found] ` <20050325034341.GV32638@waste.org>
     [not found]   ` <20050327035149.GD4053@g5.random>
2005-03-27  5:48     ` [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics Matt Mackall
2005-03-27  6:33       ` Dmitry Yusupov
2005-03-27  6:46         ` David S. Miller
2005-03-28 19:45           ` Roland Dreier
     [not found]             ` <1112042936.5088.22.camel@beastie>
2005-03-28 22:32               ` Benjamin LaHaise
2005-03-29  3:19                 ` Linux support for RDMA (was: [Ksummit-2005-discuss] Summary of 2005 Kernel Summit Proposed Topics) Roland Dreier
2005-03-30 16:00                   ` Benjamin LaHaise
2005-03-31  1:08                     ` Linux support for RDMA H. Peter Anvin

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=424CAA82.1010707@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrea@suse.de \
    --cc=bcrl@kvack.org \
    --cc=davem@davemloft.net \
    --cc=dmitry_yus@yahoo.com \
    --cc=jaganav@us.ibm.com \
    --cc=ksummit-2005-discuss@thunk.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=mpm@selenic.com \
    --cc=netdev@oss.sgi.com \
    --cc=open-iscsi@googlegroups.com \
    --cc=roland@topspin.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;
as well as URLs for NNTP newsgroup(s).