From: Roland Dreier <roland@topspincom.com>
To: Pekka Pietikainen <pp@evil.netppl.fi>
Cc: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>,
linux-kernel@vger.kernel.org
Subject: Re: Linux and system area networks
Date: 28 Jun 2001 14:46:49 -0700 [thread overview]
Message-ID: <52d77o46ra.fsf@love-boat.topspincom.com> (raw)
In-Reply-To: <20010627154140.A14908@netppl.fi> <Pine.LNX.4.33.0106281918560.32296-100000@kenzo.iwr.uni-heidelberg.de> <20010628221227.A24517@netppl.fi>
In-Reply-To: Pekka Pietikainen's message of "Thu, 28 Jun 2001 22:12:27 +0300"
Pekka> If you used sockets, I believe the normal way to use SAN
Pekka> boards is to just make them look like network cards with a
Pekka> large MTU Sure it works, but it's not very efficient :) (I
Pekka> have to admit I've not played with that kind of toys at
Pekka> all, though)
We seem to have come full circle. My original question was about
providing a better way for sockets applications to take advantage of
SAN hardware. W2K Datacenter introduces "Winsock Direct," which will
bypass the protocol stack when appropriate. The Infiniband people are
working on a "Sockets Direct" standard, which is a similar idea. No
one seems to care about this for Linux.
Roland
next prev parent reply other threads:[~2001-06-28 21:47 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
2001-06-28 17:28 ` Bogdan Costescu
2001-06-28 19:12 ` Pekka Pietikainen
2001-06-28 21:46 ` Roland Dreier [this message]
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=52d77o46ra.fsf@love-boat.topspincom.com \
--to=roland@topspincom.com \
--cc=bogdan.costescu@iwr.uni-heidelberg.de \
--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