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 91C94380; Mon, 12 Aug 2024 11:06:04 +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=1723460767; cv=none; b=eISUsstyaJ9OwB1BpFjWbGLT73k1GNU7S8wJbCEBiU7m14tjUmyiENkFSBH0PhyS7cNi8aA8j4loiF9e78g8QgZkDHTVa8ZYdBAsAGe7BDNfW9wHbeYSz9Z7PkPNSNdg7gjpPPazQOYAaoetpMtjWlk9KfURg9s4gnQIXn97/xY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1723460767; c=relaxed/simple; bh=5msWubFUrC7JH/hdT6tuEQlfTvrJRBDt3jfOM4r1dPQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=oA6sc7SJCX9WuxYLP2Y51ylstbrdB7hI+MswpH0d9bfyEqjKMVtaqSsjEOEhDApDzunSssipn3PntcDda78fdYOYtO6mCiIep/2tiNlknX/GZMFqVVwkzfDPUs+XxvB8rPt+dbrmmLyqfHyeb4BKYLUSuTFlL2MbpNk4rp9Sn6A= 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 74AC768AA6; Mon, 12 Aug 2024 13:06:00 +0200 (CEST) Date: Mon, 12 Aug 2024 13:06:00 +0200 From: Christoph Hellwig To: Sagi Grimberg Cc: Christoph Hellwig , Tariq Toukan , Jakub Kicinski , Anna Schumaker , Trond Myklebust , linux-nfs@vger.kernel.org, Boris Pismenny , John Fastabend , Maxim Mikityanskiy , Saeed Mahameed , Gal Pressman , Networking , Paolo Abeni , Eric Dumazet , "David S. Miller" , Linux Kernel Mailing List , Leon Romanovsky , Tariq Toukan Subject: Re: [Bug report] NFS patch breaks TLS device-offloaded TX zerocopy Message-ID: <20240812110600.GB14300@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> <20240812090215.GA5497@lst.de> <06a66824-cc2e-4f6d-8776-c2bd415c06f9@grimberg.me> Precedence: bulk X-Mailing-List: linux-kernel@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: <06a66824-cc2e-4f6d-8776-c2bd415c06f9@grimberg.me> User-Agent: Mutt/1.5.17 (2007-11-01) On Mon, Aug 12, 2024 at 12:13:51PM +0300, Sagi Grimberg wrote: > > > > On 12/08/2024 12:02, Christoph Hellwig wrote: >> On Tue, Aug 06, 2024 at 01:07:47PM +0300, Tariq Toukan wrote: >>> Adding Maxim Mikityanskiy, he might have some insights. >> I think the important part to find out is if the in-kernel TLS API >> has a limitation to PAGE_SIZE buffer segments, or not. > > I don't see why it should. Also note that sw tls does not suffer from > this. Maybe Jakub can add more light here in case something was missed? I don't see why it should either, but instead of assuming we should make it clear what the assumptions are before going further.