From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 973B83B71B8; Thu, 9 Jul 2026 06:22:05 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=198.137.202.133 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783578129; cv=none; b=dNqJYaQ9rb3kON1YqD8RWPhF2lAn+lhId2SxZRJyQ/FFL4WkaomIGKqQ4s4qq4yQRM+ukUxZ4/Pne1jDw3rhfoToVDfE7ttFRgfid0UOepix6jHUPrb563WM1vP2cw7awbPRrVyGS0Ivfg4N4UMqzCMutwh9zFlHElMqusvDb1k= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783578129; c=relaxed/simple; bh=p5YWmUjKmZBDzAruaws7Z66qQssX09NRcDVD+6LKOGw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Q28G1CUf5Kn3ExRwkPIm6hYaJ1hctSL9y+UDHQnkG3/1IROVC977nN/lMwP78US6qCk2NrqdQcKPtg1brwa+hl6VT6vKHMWvwAbv+Co/NTynLp4Cz9zunwtjKXaGSo2dSvbKTsz+5r1ViYxabr1T1lyV/eUm6QP+DDHF+X7LeF0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b=UN7d6eko; arc=none smtp.client-ip=198.137.202.133 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=infradead.org Authentication-Results: smtp.subspace.kernel.org; spf=none smtp.mailfrom=bombadil.srs.infradead.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="UN7d6eko" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=gF6J3GIPzB252v3fk/nA4luYZs9h9zFcInqUmdwDTgM=; b=UN7d6ekoveglcriPTF826Jme+X g4JvFxZB7+4fw3Gop5HMmI7YU3DZKH7Ston2ie0y5t53LPIkN1ui2qqT2ZJMoNMkgslveG7a+mI6C K+RaR5qVmnS91IaTnWbBLjLAPinHcWCPeiimcIqM9tdU344l3rsALhgAD1qYoFSvmsHGVtHf3ilo0 autVEdHMv0GM1+KCJwtvBx/8qEG6pRtZTw8IbT4gMNv6wU3ID6EljEvTP3wVEawo+CTvdjWZ12XJG oF0KyloGsu+Y8v0bzI6DpI0LoFm2AMq/Sf+tO3djsXwJSM1Xu8lnbXOBuYbYevROtuIe95/x4Gd9M p7nfV2uA==; Received: from hch by bombadil.infradead.org with local (Exim 4.99.1 #2 (Red Hat Linux)) id 1whi97-000000018qZ-29YS; Thu, 09 Jul 2026 06:22:05 +0000 Date: Wed, 8 Jul 2026 23:22:05 -0700 From: Christoph Hellwig To: Pranjal Shrivastava Cc: Christoph Hellwig , Matthew Wilcox , Trond Myklebust , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org, Anna Schumaker , Shivaji Kant , linux-mm@kvack.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH v2 6/7] nfs: Optimize direct I/O to use folios for requests Message-ID: References: Precedence: bulk X-Mailing-List: linux-fsdevel@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: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html On Thu, Jul 09, 2026 at 06:19:12AM +0000, Pranjal Shrivastava wrote: > On Wed, Jul 08, 2026 at 11:47:27AM +0000, Pranjal Shrivastava wrote: > > On Wed, Jul 08, 2026 at 12:48:56AM -0700, Christoph Hellwig wrote: > > > On Tue, Jul 07, 2026 at 12:08:27PM +0000, Pranjal Shrivastava wrote: > > > > Ack. I see! Thanks! > > > > > > > > Regarding the page_folio impasse, how do you suggest we proceed? Should > > > > I expose and use get_contig_folio_len() from bvec? Or should I move the > > > > NFS helper into the iov_iter lib? (or both). > > > > > > Sounds like the best way forward for now. > > > > Ack. I'll reuse get_contig_folio len and move the nfs extractor to > > iov_iter for v3. > > > > On a second thought, I guess I'd try taking a stab at writing > iov_iter_extract_folios and handle the vmalloc / slab cases for kvecs. > I believe that would be the right way to go, unless I'm missing > something obvious? Can I take a stab at it in the next version? That does sound good, but it might get you into some longer discussions.