IETF Logo Mail Archive

Re: [nfsv4] [internet-drafts@ietf.org: New Version Notification for draft-hellwig-nfsv4-rdma-layout-00.txt]

Christoph Hellwig <hch@lst.de> Wed, 19 July 2017 07:50 UTC

Return-Path: <hch@lst.de>
X-Original-To: nfsv4@ietfa.amsl.com
Delivered-To: nfsv4@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9503313170E for <nfsv4@ietfa.amsl.com>; Wed, 19 Jul 2017 00:50:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vuc492xB2es6 for <nfsv4@ietfa.amsl.com>; Wed, 19 Jul 2017 00:50:53 -0700 (PDT)
Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E5B7131BFE for <nfsv4@ietf.org>; Wed, 19 Jul 2017 00:50:53 -0700 (PDT)
Received: by newverein.lst.de (Postfix, from userid 2407) id 0594A68C4E; Wed, 19 Jul 2017 09:50:52 +0200 (CEST)
Date: Wed, 19 Jul 2017 09:50:51 +0200
From: Christoph Hellwig <hch@lst.de>
To: David Noveck <davenoveck@gmail.com>
Cc: Chuck Lever <chucklever@gmail.com>, Christoph Hellwig <hch@lst.de>, "nfsv4@ietf.org" <nfsv4@ietf.org>
Message-ID: <20170719075051.GB21462@lst.de>
References: <20170702231000.GA2564@lst.de> <26A3EDDF-200C-49F2-934B-CD9155AECE88@gmail.com> <CADaq8jdK+nSDBy6xr=VU-eWX8LMvWuZZQdy5VMKrbBrh3RPVKA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CADaq8jdK+nSDBy6xr=VU-eWX8LMvWuZZQdy5VMKrbBrh3RPVKA@mail.gmail.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfsv4/ZeBfC3c4znFvlAAvBGoNiaWSo50>
Subject: Re: [nfsv4] [internet-drafts@ietf.org: New Version Notification for draft-hellwig-nfsv4-rdma-layout-00.txt]
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfsv4/>
List-Post: <mailto:nfsv4@ietf.org>
List-Help: <mailto:nfsv4-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jul 2017 07:50:54 -0000

On Mon, Jul 17, 2017 at 07:56:31AM -0400, David Noveck wrote:
> An alternative is for the MDS to do the bind operation as part of assigning
> the layout, which
> it can do as long as it knows the connection.  One possibility is for the
> to client to pass
> a description of the chosen connection as a layout-hint.  Another is for
> the MDS to be able
> to find out the set of possible connections, havie it choose one, and let
> the client know,
> in the layout, which connection is associated with the layout.

My idea (although it's not described very well) is that a device_addr4
describes a specific QP.  So by referencing that addr from a layout
we're bound to the specific QP.

> The simplest way to deal with this, although maybe not the best, is to
> consider the
> connection break as  effectively revoking all associated layouts.  The
> client needs
> to get new layouts to replace the ones lost.

Agreed.

v2.46.0 | Report a Bug | By Email | System Status