Re: [nfsv4] Sharing same TCP connection for NFSv3 and NFSv4 traffic

Mitchell Erblich <erblichs@earthlink.net> Thu, 19 August 2010 03:26 UTC

Return-Path: <erblichs@earthlink.net>
X-Original-To: nfsv4@core3.amsl.com
Delivered-To: nfsv4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 393A63A6AC5 for <nfsv4@core3.amsl.com>; Wed, 18 Aug 2010 20:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599]
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 bm27Mm6e95RX for <nfsv4@core3.amsl.com>; Wed, 18 Aug 2010 20:25:58 -0700 (PDT)
Received: from elasmtp-scoter.atl.sa.earthlink.net (elasmtp-scoter.atl.sa.earthlink.net [209.86.89.67]) by core3.amsl.com (Postfix) with ESMTP id 513383A6B43 for <nfsv4@ietf.org>; Wed, 18 Aug 2010 20:20:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mKqS/EcmAMoTPOvclEFKgwpOgd9VBzecOghlpczb8jDFAe7vRq2XIHmdG87osfLv; h=Received:Subject:Mime-Version:Content-Type:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [4.246.234.112] (helo=dialup-4.246.234.112.dial1.sanjose1.level3.net) by elasmtp-scoter.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <erblichs@earthlink.net>) id 1OlvgN-0006rH-PL; Wed, 18 Aug 2010 23:20:48 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Mitchell Erblich <erblichs@earthlink.net>
In-Reply-To: <187766653.794656.1282176511670.JavaMail.root@erie.cs.uoguelph.ca>
Date: Wed, 18 Aug 2010 20:20:41 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <4D3C9B3C-3C3B-45DC-98B6-3D00F8D3F2B7@earthlink.net>
References: <187766653.794656.1282176511670.JavaMail.root@erie.cs.uoguelph.ca>
To: Rick Macklem <rmacklem@uoguelph.ca>
X-Mailer: Apple Mail (2.1081)
X-ELNK-Trace: 074f60c55517ea841aa676d7e74259b7b3291a7d08dfec793506f33e919857ba608de979db7ea8e2350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.246.234.112
Cc: Pranoop Erasani <Pranoop.Erasani@netapp.com>, nfsv4@ietf.org
Subject: Re: [nfsv4] Sharing same TCP connection for NFSv3 and NFSv4 traffic
X-BeenThere: nfsv4@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NFSv4 Working Group <nfsv4.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/nfsv4>, <mailto:nfsv4-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Thu, 19 Aug 2010 03:26:00 -0000

On Aug 18, 2010, at 5:08 PM, Rick Macklem wrote:

>> 
>> Out of curiosity, Do any of the clients that you work on or that you
>> know of, share the same TCP connection for NFSv3 and NFSv4 traffic?
>> 
> Nope w.r.t the FreeBSD one, rick
> 
> 
I am not sure what "share the same TCP connection" means here.

If a client/HTTP  starts up a later connection to the same dest,
then some implementations have the later at least peak into
TCP info of the former to improve performance. It is specified
in a spec.

Whether some TCP structs have more than a single reference
count in an implementation should not be relevent.

Mitchell Erblich
 


> _______________________________________________
> nfsv4 mailing list
> nfsv4@ietf.org
> https://www.ietf.org/mailman/listinfo/nfsv4