From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CBB9B178378; Mon, 12 Aug 2024 13:23:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.95.11.211 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723469041; cv=none; b=nNe3FDJDJfEFD7WvPnHt12ngqlF65vjWUrIs+LmnDecuJTLsexltYFLfOoUXhM70G+r2t5uhuJa7Y3xdDccQ1iSlnzBTNNop2IVnYXlhQDHvgIAOHsLTYKGvzTkTiMNCgDDa18ReVAh9O7eCyfZxlJ/ORgALAQ0iQUDp633PWMY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723469041; c=relaxed/simple; bh=VuI+wPFxg0qN0XzAAYkHh993rdpl2H1G9OpKgKCGieE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=dUBMHFgacRJk6yTYYkq7lf1Z7tsMp23f/YV6w6rRiivk0tzkD+Toda1vNzuz5NwEAGz7LK1qhp0BH6E3NSpA73sRNUHmIlSByW1yi4dHkWTyYBIJ69oCc0cMMFxRAxd62j6iQkQUK6XI9O0HLY1Aozi5F4IZaso9ILSsPOFR1is= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de; spf=pass smtp.mailfrom=lst.de; arc=none smtp.client-ip=213.95.11.211 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lst.de Received: by verein.lst.de (Postfix, from userid 2407) id 43C42227A87; Mon, 12 Aug 2024 15:23:54 +0200 (CEST) Date: Mon, 12 Aug 2024 15:23:54 +0200 From: Christoph Hellwig To: Tariq Toukan Cc: Sagi Grimberg , Christoph Hellwig , Anna Schumaker , Trond Myklebust , linux-nfs@vger.kernel.org, Boris Pismenny , John Fastabend , Jakub Kicinski , Maxim Mikityanskiy , David Howells , Sabrina Dubroca , Mina Almasry , Saeed Mahameed , Gal Pressman , Networking , Paolo Abeni , Eric Dumazet , "David S. Miller" , Linux Kernel Mailing List , Leon Romanovsky , Tariq Toukan , drort@nvidia.com Subject: Re: [Bug report] NFS patch breaks TLS device-offloaded TX zerocopy Message-ID: <20240812132354.GA23655@lst.de> References: <77fb3db5-7a59-4879-b9c2-d3408fcf67e8@grimberg.me> <4f42fac4-2a4e-426a-be86-1f4bb79987b4@gmail.com> <3e08421f-91ac-4bd1-9886-3d5ecf9afa04@grimberg.me> <8683155c-79ad-4090-9aff-fc8d765b096b@gmail.com> <65a77bbb-b7dc-40d8-b09f-c0cf0cb01271@gmail.com> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) On Mon, Aug 12, 2024 at 04:15:35PM +0300, Tariq Toukan wrote: >> Can you explain where in your test is NFS used? Is the nginx server runs >> on an NFS mount? > > I checked with the team. > The requested file, as well as the wrk and nginx apps, all reside on an NFS > mount. So maybe I misunderstood the workload. You aren't using the NFS over TLS, but your are webserving using sendfile with the TLS offload, with the data coming from a NFS share that isn't using TLS? In that case NFS really is just the trigger here and you'd see the exact same behavior when serving from another large folios enabled file system like XFS, or probably also when serving from anonymous memory. This very clearly points to a debug in the hardware TLS offload.