public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@evil.netppl.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux and system area networks
Date: Wed, 27 Jun 2001 15:41:40 +0300	[thread overview]
Message-ID: <20010627154140.A14908@netppl.fi> (raw)
In-Reply-To: <200106261236.HAA79784@tomcat.admin.navo.hpc.mil>
In-Reply-To: <200106261236.HAA79784@tomcat.admin.navo.hpc.mil>

On Tue, Jun 26, 2001 at 07:36:30AM -0500, Jesse Pollard wrote:
> > I think you misunderstood the point.  Microsoft is providing this WSD
> > DLL as a standard part of W2K now.  This means that hardware vendors
> > just have to write a SAN service provider, and all Winsock-using
> > applications benefit transparently.  No matter how good your TCP/IP
> > implementation is, you still lose (especially in latency) compared to
> > using reliable hardware transport.  Oracle-with-VI and DAFS-vs-NFS
> > benchmarks show this quite clearly.
> 
> You do loose in security. You can't use IPSec over such a device without
> some drastic overhaul.
And the performance gains are not as obvious as one would hope, as
 there is some overhead caused by the WSD switch software
that transparently maps connections onto standard IP networks and SAN
boards depending on who you are talking to.

For some performance comparisions comparing WSD/native VI/TCP, there's
a paper called "WSDLite: a Lightweight Alternative to Windows Sockets Direct
Path", there's a link to the paper at http://citeseer.nj.nec.com/388853.html
(seems you have to use the Cached: links)

Providing a wrapper library for use with Infiniband and the current
SAN boards like WSD would probably be a useful exercise, but to really get
good performance (especially latency-wise) you probably want to use
something like MPI. For many applications a wrapper will be enough, though.
-- 
Pekka Pietikainen

  reply	other threads:[~2001-06-27 12:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-26 12:36 Linux and system area networks Jesse Pollard
2001-06-27 12:41 ` Pekka Pietikainen [this message]
2001-06-28 17:28   ` Bogdan Costescu
2001-06-28 19:12     ` Pekka Pietikainen
2001-06-28 21:46       ` Roland Dreier
2001-06-29  2:33         ` Bernd Eckenfels
     [not found] <mailman.993492125.21454.linux-kernel2news@redhat.com>
2001-06-25 22:30 ` Pete Zaitcev
2001-06-25 22:55   ` Roland Dreier
2001-06-26  0:14     ` Alan Cox
2001-06-26  0:08   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2001-06-25 17:59 Roland Dreier

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=20010627154140.A14908@netppl.fi \
    --to=pp@evil.netppl.fi \
    --cc=linux-kernel@vger.kernel.org \
    /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