public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: "Woodruff, Robert J" <woody@co.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tcp/ip offload card driver
Date: Sat, 11 May 2002 22:46:04 -0400	[thread overview]
Message-ID: <200205120246.g4C2k4t04510@devserv.devel.redhat.com> (raw)
In-Reply-To: <mailman.1021067221.3300.linux-kernel2news@redhat.com>

>>Don't forget 
>>that with 64 bit PCI that the limit of the bus has been raised, and with 
>>impending technologies like Infiniband and Hypertransport that limit 
>>will be raised again.
> 
> If people are interesting in discussing ideas on how InfiniBand 
> networking (sockets direct (SDP) and IP over InfiniBand) should be/could 
> be implemented and you are planning on attending the Linux Symposium
> in Ottawa in June, there is an InfiniBand BOF session where we could 
> discuss and exchange ideas on this topic. 

The more people, the merrier, but I am afraid that may subvert
the BOF. The problem is that nobody showed any convincing
proof that TOE actually works with benchmarks, let alone
in the real life. It was all a pretty groundless speculation so far.
I was on a conf call a week ago, where a guy said: "We implemented
TOE in the NT stack and achieved 100% speed-up", and I was like
"huh? and it tells me what? That NT stack was crap to begin with?"
I would like to keep the BOF on practical topics of Infiniband
implementation in Linux by any means necessary. TOE people
are welcome to come back when they have something working,
and when we know how fast the regular IP over Infiniband can go.

-- Pete

       reply	other threads:[~2002-05-12  2:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1021067221.3300.linux-kernel2news@redhat.com>
2002-05-12  2:46 ` Pete Zaitcev [this message]
2002-05-13 16:17 Tcp/ip offload card driver Woodruff, Robert J
     [not found] <Pine.LNX.4.44.0205121335050.14675-100000@filesrv1.baby-dra gons.com>
2002-05-12 22:26 ` Lincoln Dale
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10 21:43 Woodruff, Robert J
2002-05-10 18:39 Nivedita Singhvi
     [not found] <mailman.1021046154.26338.linux-kernel2news@redhat.com>
2002-05-10 17:55 ` Pete Zaitcev
2002-05-10 17:46   ` David S. Miller
2002-05-10 17:36 Nivedita Singhvi
2002-05-10 14:48 chen, xiangping
2002-05-10 14:43 ` David S. Miller
2002-05-10 15:11   ` Pedro M. Rodrigues
2002-05-10 15:04     ` David S. Miller
2002-05-10 16:59       ` Jesse Pollard
2002-05-11 22:23         ` Oliver Xymoron
2002-05-10 15:31     ` Jeff Garzik
2002-05-10 15:51       ` Nicholas Harring
2002-05-10 15:49         ` David S. Miller
2002-05-10 16:04           ` Nicholas Harring
2002-05-10 16:09         ` Joel Jaeggli
2002-05-12  0:55         ` john slee
2002-05-12 17:36           ` Mr. James W. Laferriere
2002-05-10 18:36       ` Eric W. Biederman
2002-05-10 16:02     ` Mark Hahn
2002-05-10 15:12   ` Jeff Garzik
2002-05-10 15:07     ` David S. Miller
2002-05-11  1:53       ` Lincoln Dale
2002-05-12  2:56         ` David S. Miller

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=200205120246.g4C2k4t04510@devserv.devel.redhat.com \
    --to=zaitcev@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=woody@co.intel.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