Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp255714pxx; Thu, 29 Oct 2020 01:38:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyBWbXKWZDpTA92ZmKgGtCkVYP9r3DNJuOMT1ukbSTOCUxRvJ279ipD0SzpbXuSqMPBvcbx X-Received: by 2002:a17:906:4e56:: with SMTP id g22mr764457ejw.49.1603960684728; Thu, 29 Oct 2020 01:38:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603960684; cv=none; d=google.com; s=arc-20160816; b=OOGScyi72GglFQ0KAYxXSRfCmfATplCXWR8CGHHCqJcQliQO5UDrHf15ySTaRI+0nv NoQWUMkU8wJHUyRWXYwlBONdTiM/Rf6lP7fy/BjsyhB4g0KBl9PuC4MlG/pEE+ODpxe0 HSs3VVbCAH+1jNXB+amcpExTvHE5XMZkuXfHCf/kR8abTj+2dQAhwBkqGvQ+isQqPmfL IxvpaOS+nxatpZP2B3vy6eIuQGUe6QgYrHgCuLATrw+7AQBQSOORpNoogrxLZtp8lLQQ nuKQ3VUQF9t4rSJVwTe7upKpuMneoguIi0v4QIXL+OjcqRotnAR4xzGzCkf9fL6JL8wA NZwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=BSxR9G99QZZs9WQft0msIQGjwPYUjz+YA1ZtZ90swg4=; b=QoDPASp3vSft4IRFGVJ/Vqe5XVNaBc4m2/nQImZwQoqv/OLxVMsVd+fdvciK4o4VQ7 UEW6oQul+7u1uMefsV2Vbe8KfnLYWfID7M4+xckolOv/PjMYf2BX5SgZ9QVFuAl3/Qxx tyCDSOM50oYDgGc9hCqAGNklfqocl9orNW6tXXCoTRt7vMIsil/8fVQFEsNUJa1EDeQF S2pcH2qDDzkPeayxP9DhguB6VOK6GZSlrmafuDgbC/dtlLTXEoCZdPyVa3J7fq9Tpc7w wjG8KPf/2y5KdxK60DzpPtoL5x1ERO5sH2CDsaaXUl7Y3lVny2kJffsuqsY+SAtBLOnx L/EQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ztI4+WMU; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v9si1757041edd.40.2020.10.29.01.37.40; Thu, 29 Oct 2020 01:38:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ztI4+WMU; spf=pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-nfs-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2391012AbgJ2A4W (ORCPT + 99 others); Wed, 28 Oct 2020 20:56:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:60520 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731617AbgJ1WRg (ORCPT ); Wed, 28 Oct 2020 18:17:36 -0400 Received: from localhost (unknown [213.57.247.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 75ADC22275; Wed, 28 Oct 2020 07:16:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1603869365; bh=BSxR9G99QZZs9WQft0msIQGjwPYUjz+YA1ZtZ90swg4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ztI4+WMUvZa0GWBnfKsmFMQgiwsXUHvSmBC0cGW2zG4/jBiYdYKeimxRCZUGVtSzY NKX8OJOH0OC8jpwXKQEE570YqQVdwcjy+bJhU5rpVWZKm+OySoGTEKtYOuCbmWyfR9 X0M3K4XN+1qkqv+KA2ebktet80+pHQUHutl5NI5o= Date: Wed, 28 Oct 2020 09:16:01 +0200 From: Leon Romanovsky To: Chuck Lever Cc: Linux NFS Mailing List , linux-rdma@vger.kernel.org Subject: Re: [PATCH 00/20] NFSD support for multiple RPC/RDMA chunks Message-ID: <20201028071601.GA114054@unreal> References: <160373843299.1886.12604782813896379719.stgit@klimt.1015granger.net> <20201027060823.GF4821@unreal> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-nfs@vger.kernel.org On Tue, Oct 27, 2020 at 09:24:54AM -0400, Chuck Lever wrote: > Hi Leon- > > > On Oct 27, 2020, at 2:08 AM, Leon Romanovsky wrote: > > > > On Mon, Oct 26, 2020 at 02:53:53PM -0400, Chuck Lever wrote: > >> This series implements support for multiple RPC/RDMA chunks per RPC > >> transaction. This is one of the few remaining generalities that the > >> Linux NFS/RDMA server implementation lacks. > >> > >> There is currently one known NFS/RDMA client implementation that can > >> send multiple chunks per RPC, and that is Solaris. Multiple chunks > >> are rare enough that the Linux NFS/RDMA implementation has been > >> successful without this support for many years. > > > > So why do we need it? Solaris is dead, and like you wrote Linux systems > > work without this feature just fine, what are the benefits? Who will use it? > > The Linux NFS implementation is living. We can add the ability > to provision multiple chunks per RPC to the Linux NFS client at > any time. > > Likewise any actively developed NFS/RDMA implementation can add > this feature. The RPC/RDMA version 1 protocol does not have the > ability to communicate the maximum number of chunks the server > will accept per RPC. > > Other server implementations do support multiple chunks per RPC. > The Linux NFS/RDMA server implementation has always been incomplete > in this regard. > > And the Linux NFS server implementation (the non-transport specific > part) already supports multiple data payloads per NFSv4 COMPOUND. Thanks, I just got different feeling then I read the cover letter. You presented it like no one needs this feature. Thanks