Re: [rddp] [Ips] Storage Maintenance (storm) BOF reminder & requests

Caitlin Bestler <cait@asomi.com> Tue, 24 March 2009 20:33 UTC

Return-Path: <cait@asomi.com>
X-Original-To: rddp@core3.amsl.com
Delivered-To: rddp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A498E3A69BD for <rddp@core3.amsl.com>; Tue, 24 Mar 2009 13:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.971
X-Spam-Level:
X-Spam-Status: No, score=-1.971 tagged_above=-999 required=5 tests=[AWL=0.294, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TcCKIzlC01kU for <rddp@core3.amsl.com>; Tue, 24 Mar 2009 13:33:20 -0700 (PDT)
Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by core3.amsl.com (Postfix) with ESMTP id EECC93A6A93 for <rddp@ietf.org>; Tue, 24 Mar 2009 13:33:19 -0700 (PDT)
Received: (qmail 25117 invoked from network); 24 Mar 2009 20:34:11 -0000
Received: from wmail1.sea5.speakeasy.net ([69.17.117.157]) (envelope-sender <cait@asomi.com>) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for <rddp@ietf.org>; 24 Mar 2009 20:34:11 -0000
Received: from wmail.speakeasy.net (localhost [127.0.0.1]) by wmail1.sea5.speakeasy.net (Postfix) with ESMTP id E9C9C7FD1; Tue, 24 Mar 2009 13:34:10 -0700 (PDT)
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-Mailer: AtMail - 198.186.3.73 - cait@asomi.com
Date: Tue, 24 Mar 2009 13:34:10 -0700
X-Origin: 198.186.3.73
Message-Id: <52130.1237926850@asomi.com>
To: Bernard Metzler <BMT@zurich.ibm.com>, "Robert D. Russell" <rdr@iol.unh.edu>
From: Caitlin Bestler <cait@asomi.com>
Cc: rddp@ietf.org
Subject: Re: [rddp] [Ips] Storage Maintenance (storm) BOF reminder & requests
X-BeenThere: rddp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF Remote Direct Data Placement \(rddp\) WG" <rddp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rddp>
List-Post: <mailto:rddp@ietf.org>
List-Help: <mailto:rddp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rddp>, <mailto:rddp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2009 20:33:20 -0000

>On Tue Mar 24  8:26 , Bernard Metzler <BMT@zurich.ibm.com> wrote:
>Hi Robert,
>
>an RNIC would be happy to transition an established
>socket into RDMA mode if the user wants to. No problem -
>as far as i know - to transition from TOE mode to RDMA mode at least.
>It is a question of envrionmental support to allow that. To allow that,
>the environment (aka OFED) wold have to integrate
>late socket translation, which allows RNIC drivers to officially
>do TOE to RDMA mode transition or to take over a socket
>
>(where the OS would have to expose a well-defined
>TCP context reallocation scheme).
>Maybe it is not a good idea to change an end-to-end
>protocol because a host environment has functional limitations
>which may stem from historical transport (IB) limitations
>or OS considerations.
>

I agree with Bernard.

Conventional RNICs are indeed transitioning streaming mode TCP connections
to MPA for iWARP in full compliance with the existing RFCs.

What Linux has not implemented is transitioning a host-created streaming mode
TCP connection to an offload device held streaming mode TCP connection.
That is a very complex issue, which fortunately for this forum, is out of scope.