From: Pete Zaitcev <zaitcev@redhat.com>
To: roland@hellmouth.digitalvampire.org, linux-kernel@vger.kernel.org
Subject: Re: Linux and system area networks
Date: Mon, 25 Jun 2001 18:30:13 -0400 [thread overview]
Message-ID: <200106252230.f5PMUDE26001@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.993492125.21454.linux-kernel2news@redhat.com>
In-Reply-To: <mailman.993492125.21454.linux-kernel2news@redhat.com>
> I'd like to find out if anyone has thought about how Linux will handle
> some of the new network technologies people are starting to push.
> Specifically I'm talking about "System Area Networks," that is, things
> like Infiniband, as well as TCP/IP offload.
Infiniband is doing relatively well, as much as anything can
with Intel at the helm (see "Itanic"). This has nothing to
do with TCP/IP offload, which is an extremely stupid idea.
The whole thing stems from a desire by vendors to sell
"smart" (== very expensive) NICs.
RDMA in Infiniband is, in my view, a little more than
traditional DMA in any other advanced server I/O bus.
Sun UPA is packetized, for instance.
> The rough idea is that WSD is a new user space library that looks at
> sockets calls and decides if they have to go through the usual kernel
> network stack, or if they can be handed off to a "SAN service
> provider" which bypasses the network stack and uses hardware reliable
> transport and possibly RDMA.
That can be done in Linux just as easily, using same DLLs
(they are called .so for "shared object"). If you look
at Ashok Raj's Infi presentation, you may discern "user-level
sockets", if you look hard enough. I invite you to try, if
errors of others did not teach you anything.
> This means that all applications that use Winsock benefit from the
> advanced network hardware. Also, it means that Windows is much easier
> for hardware vendors to support than other OSes. For example,
> Alacritech's TCP/IP offload NIC only works under Windows. Microsoft
> is also including Infiniband support in Windows XP and Windows 2002.
IMHO, Alacritech is about to join scores and scores of vendors
who tried that before. Customers understand very soon that
a properly written host based stack works much better in
the face of a changing environment: Faster CPUs, new CPUs
(IA-64), new network protocols (ECN). Besides, it is easy
to "accelerate" a bad network stack, but try to outdo a
well done stack.
> So I guess my question is whether anyone has started thinking about
> the architectural changes needed to make System Area Networking and
> TCP/IP offload easier under Linux.
Pretty much zero-copy that DaveM and Co. do addresses this.
-- Pete
next parent reply other threads:[~2001-06-25 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.993492125.21454.linux-kernel2news@redhat.com>
2001-06-25 22:30 ` Pete Zaitcev [this message]
2001-06-25 22:55 ` Linux and system area networks Roland Dreier
2001-06-26 0:14 ` Alan Cox
2001-06-26 0:08 ` Alan Cox
2001-06-26 12:36 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
2001-06-29 2:33 ` Bernd Eckenfels
-- 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=200106252230.f5PMUDE26001@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@hellmouth.digitalvampire.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