From: Roland Dreier <roland@topspin.com>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@redhat.com>, Jordi Ros <jros@xiran.com>,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org,
netdev@oss.sgi.com, alan@storlinksemi.com
Subject: Re: TCP IP Offloading Interface
Date: 15 Jul 2003 18:51:39 -0700 [thread overview]
Message-ID: <52fzl7s0gk.fsf@topspin.com> (raw)
In-Reply-To: <1058329895.1796.28.camel@jzny.localdomain>
jamal> What about infiniband which has all this built in
jamal> offloading?
We're seeing some pretty good numbers (well above 5 Gb/sec, basically
PCI-X 64bit/133MHz limited) with sockets direct (SDP) on top of
InfiniBand. This is running standard sockets applications, just using
the AIO patches for kernel 2.4. Latency is also much better than TCP
on top of ethernet, although this is mostly just due to the
underlying transport.
- Roland
next prev parent reply other threads:[~2003-07-16 1:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E3738FB497C72449B0A81AEABE6E713C027A43@STXCHG1.simpletech.com>
2003-07-15 5:51 ` TCP IP Offloading Interface David S. Miller
2003-07-16 5:02 ` jamal
2003-07-16 1:51 ` Roland Dreier [this message]
2003-07-15 16:28 David griego
-- strict thread matches above, loose matches on Subject: below --
2003-07-13 7:33 Alan Shih
2003-07-13 7:48 ` David S. Miller
2003-07-13 16:22 ` Roland Dreier
2003-07-13 16:31 ` Alan Cox
2003-07-13 16:49 ` Jeff Garzik
2003-07-13 16:58 ` Jeff Garzik
2003-07-13 23:02 ` David S. Miller
2003-07-13 23:35 ` Larry McVoy
2003-07-13 23:40 ` David S. Miller
2003-07-13 23:54 ` Larry McVoy
2003-07-13 23:53 ` David S. Miller
2003-07-14 0:22 ` Larry McVoy
2003-07-14 0:24 ` David S. Miller
2003-07-14 0:48 ` Larry McVoy
2003-07-14 0:46 ` Valdis.Kletnieks
2003-07-14 0:42 ` David S. Miller
2003-07-16 2:46 ` Matt Porter
2003-07-14 0:20 ` Roland Dreier
2003-07-14 0:28 ` David S. Miller
2003-07-16 2:37 ` Matt Porter
2003-07-13 14:51 ` Jeff Garzik
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=52fzl7s0gk.fsf@topspin.com \
--to=roland@topspin.com \
--cc=alan@storlinksemi.com \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jros@xiran.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.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).