linux-kernel - Re: [PATCH v3 0/4] NFSD: Impl multiple extents in block/scsi layoutget

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <175959837985.2025.4024778494628599093.b4-ty@oracle.com>
Date: Sat,  4 Oct 2025 13:20:12 -0400
From: Chuck Lever <cel@...nel.org>
To: Christoph Hellwig <hch@...radead.org>,
	Dai Ngo <Dai.Ngo@...cle.com>,
	Jeff Layton <jlayton@...nel.org>,
	NeilBrown <neil@...wn.name>,
	Olga Kornievskaia <okorniev@...hat.com>,
	Tom Talpey <tom@...pey.com>,
	Sergey Bashirov <sergeybashirov@...il.com>
Cc: Chuck Lever <chuck.lever@...cle.com>,
	linux-nfs@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/4] NFSD: Impl multiple extents in block/scsi layoutget

From: Chuck Lever <chuck.lever@...cle.com>

On Fri, 03 Oct 2025 12:11:02 +0300, Sergey Bashirov wrote:
> Implement support for multiple extents in the LAYOUTGET response
> for two main reasons.
> 
> First, it avoids unnecessary RPC calls. For files consisting of many
> extents, especially large ones, too many LAYOUTGET requests are observed
> in Wireshark traces.
> 
> [...]

Applied to nfsd-testing, thanks!

[1/4] NFSD/blocklayout: Fix minlength check in proc_layoutget
      commit: b94708d49420881366669b7010269f159a6e1b70
[2/4] NFSD/blocklayout: Extract extent mapping from proc_layoutget
      commit: 88f8b3f8c4fc8c351aaae49d0fec4e7b5e6ad0db
[3/4] NFSD/blocklayout: Introduce layout content structure
      commit: 76fc273123889e9b1629fc9f1ec40465dbda1a73
[4/4] NFSD/blocklayout: Support multiple extents per LAYOUTGET
      commit: 8a3c46f07fb5c3cd6c1cc807d9a22e1531100625

--
Chuck Lever <chuck.lever@...cle.com>