netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Wise <swise@opengridcomputing.com>
To: Glenn Grundstrom <ggrundstrom@NetEffect.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	rdreier@cisco.com, ewg@lists.openfabrics.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 3/14] nes: connection manager routines
Date: Thu, 09 Aug 2007 16:06:05 -0500	[thread overview]
Message-ID: <46BB81BD.2040904@opengridcomputing.com> (raw)
In-Reply-To: <5E701717F2B2ED4EA60F87C8AA57B7CC07443E9D@venom2>



Glenn Grundstrom wrote:
> This code is far from a TCP stack.  It's main purpose is to exchange
> RDMA MPA request/response messages that are required by the iWarp specs
> and therefore needed by our hardware.  All RNIC hardware vendors need
> this MPA message exchange, including those already accepted into
> kernel.org.  Do you have an alternative suggestion?
> 

For the record, the existing linux RNICS don't exactly work this way:

Ammasso handles all TCP connection setup and MPA negotiation in HW/FW. 
The connection setup interface between the RNIC and host driver are 
strictly for RDMA connections.

Chelsio has a message based interface to the HW/FW for establishing
TCP connections and exchanging data in streaming mode.  No TCP
processing is done in the driver.

Steve.

      reply	other threads:[~2007-08-09 21:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08  0:50 [PATCH 3/14] nes: connection manager routines ggrundstrom
2007-08-08  1:46 ` Jeff Garzik
2007-08-09 17:37   ` Roland Dreier
2007-08-08 12:41 ` Andi Kleen
2007-08-08 15:31   ` Glenn Grundstrom
2007-08-09 21:06     ` Steve Wise [this message]

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=46BB81BD.2040904@opengridcomputing.com \
    --to=swise@opengridcomputing.com \
    --cc=andi@firstfloor.org \
    --cc=ewg@lists.openfabrics.org \
    --cc=ggrundstrom@NetEffect.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdreier@cisco.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).