Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp5299106ybi; Tue, 11 Jun 2019 23:45:06 -0700 (PDT) X-Google-Smtp-Source: APXvYqzVghYD57WWoYH5eDd0Kqhxqw7teaIpZgY5Uc5snP0OYUg1Rs28zbbCjylup9i8bzjdf7xB X-Received: by 2002:a63:5457:: with SMTP id e23mr24566303pgm.307.1560321906197; Tue, 11 Jun 2019 23:45:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560321906; cv=none; d=google.com; s=arc-20160816; b=F33b6uB8njDFKp90YcPnpt/3KQ59/0yjVwh1FUPaKIaWNIBGDBovC/pUFS7/JCY+N/ aAMX/S4hHRKu9x4n84kNeG5FThfHHmUWBzoyth0kNMdVQBoqpeZRRniZ7mgAqh/tJHOH 9mqSywzl01AR8FrYswdhAuLbVWjbpiemg8NBJpFxKFVXP4dUSsqvlheU+V0vVL3wqFoL o2Y3LHrHVKtgn9d1AGyEGcFJ05RO8lgNpyJ5PxyfGwLZnGQJgX0YWk8JYklTbkhI8Izi MW8brN4HzqRS8oD5+1HOVDV73eWe7fyhvZ7LujaflhdTcXUR7m5JhZjt112gLH87vQ8A +n7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:references :in-reply-to:subject:cc:date:to:from; bh=uYIgV72lrilsdv3mdZbD1/+OCU2AzFzzrDb1sMmA04w=; b=C8fuFJaysQgeUhh8XACGOoOt5ie1dZIfatMasuZJBelBq89MJ1uYmywnxaGlTxYUrz I+HO5CshQyxw4ZrKdQFd5ttMwodYcL8WcRDdYFs36I81dG+EoA2MW7XXfBIhLDuljqR0 YsemU7J2fqwNyqLVBYHmXVrjq0iBy7RXlPci1XaKUTaCEEJ3uoNslwRQV8lBvZEb/La0 ozotCOJGRFG+tXlnByY1VX7K3GnT9u/OdruFY7A5GcOMs0jde0gWABFRttHzg4kP9db4 SA1eIAx0SuOqO/j2dfHdK6jAGC+XceCqnJkCUV+po6Y38JcaFUaNdyWfi8gyu7Xid6Rn zstA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p15si14968073pgj.191.2019.06.11.23.44.32; Tue, 11 Jun 2019 23:45:06 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2436970AbfFKWzv (ORCPT + 99 others); Tue, 11 Jun 2019 18:55:51 -0400 Received: from mx2.suse.de ([195.135.220.15]:55124 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2436750AbfFKWzv (ORCPT ); Tue, 11 Jun 2019 18:55:51 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 5FC91AF0C; Tue, 11 Jun 2019 22:55:50 +0000 (UTC) From: NeilBrown To: Tom Talpey , Olga Kornievskaia , Chuck Lever Date: Wed, 12 Jun 2019 08:55:40 +1000 Cc: Anna Schumaker , Trond Myklebust , Linux NFS Mailing List Subject: Re: [PATCH 0/9] Multiple network connections for a single NFS mount. In-Reply-To: References: <155917564898.3988.6096672032831115016.stgit@noble.brown> <001DED71-0E0D-46B1-BA34-84E6ACCBB79F@oracle.com> <87muj3tuuk.fsf@notabene.neil.brown.name> <4316E30B-1BD7-4F0E-8375-03E9F85FFD2B@oracle.com> <87lfy9vsgf.fsf@notabene.neil.brown.name> <3B887552-91FB-493A-8FDF-411562811B36@oracle.com> <16D30334-67BE-4BD2-BE69-1453F738B259@oracle.com> Message-ID: <87ftofwx3n.fsf@notabene.neil.brown.name> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-nfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, Jun 11 2019, Tom Talpey wrote: > On 6/11/2019 5:10 PM, Olga Kornievskaia wrote: ... >>=20 >> Solaris has it, Microsoft has it and linux has been deprived of it, >> let's join the party. > > Let me be clear about one thing - SMB3 has it because the protocol > is designed for it. Multichannel leverages SMB2 sessions to allow > retransmit on any active bound connection. NFSv4.1 (and later) have > a similar capability. > > NFSv2 and NFSv3, however, do not, and I've already stated my concerns > about pushing them too far. I agree with your sentiment, but for these > protocols, please bear in mind the risks. NFSv2 and NFSv3 were designed to work with UDP. That works a lot like one-connection-per-message. I don't think there is any reason to think NFSv2,3 would have any problems with multiple connections. NeilBrown --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEG8Yp69OQ2HB7X0l6Oeye3VZigbkFAl0AMWwACgkQOeye3VZi gbmWMBAAgjh/jOHmBNhvFuLJDfiF7Vr21xsAa5L0z+WW1nJVloibzL+daWXuKXF9 J4OGW/NesYfpMV9REgrrRFVgwx3qhXk6+w+5HPJCq9uzeNXNPVtIeLELlhlJX++f kWlCyWCG611v15zFRJX7ZCPQ0espqVOk3MlZmIDqaBynJZNeSZnAl9ehKdj2mvNl V+rVdq5l4cndp0KXGxSyl30CvRjc81+C9/+E1OjB3iG29/ukAw72AG/UH/5NBFf6 mB+48Lb4ZquoLyI693NO+/xO2i0YdNPw9/JmXV5gpYF/ZDiBdd/4qs1JHlD0hAqK jwK1nBICg4W0COTw37WncgjJJJzFCbF0xmg0UAevGMYL9wMgYHSfVGZJCY5h+pp6 HGE46lJ0qI0F+G0/L7VWdzrHMPlpmZhzi+qAKMn2Qj6xK93yC29AO0kcG8gOPDRG PThT/1gbzLfDwcEqpGTfhgalnSfK0Mm0uh8iEERd9GTKYZdcMaGSlLn3i8X7sROp brPa3OtAyuXWYwpyanyfjloOCGX+fywq0cot+63h0eoxEYxeG0Me8upWFqkfql4/ W5jkaqTmQqSp1lI7bu1hXgwucm8bmSy6zq3jaJApHD7pIdLwxlkaGkAWLqImKAU2 YNGGcLTAsro0G+r5j6gzRlFeitgGYsUP890qTOU4qLIdy7bjfp8= =NxyM -----END PGP SIGNATURE----- --=-=-=--