linux-kernel - [RFC PATCH 0/2] Add mru cache for inode to zone allocation mapping

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-next>] [day] [month] [year] [list]

Message-ID: <20250430084117.9850-1-hans.holmberg@wdc.com>
Date: Wed, 30 Apr 2025 08:41:20 +0000
From: Hans Holmberg <Hans.Holmberg@....com>
To: "linux-xfs@...r.kernel.org" <linux-xfs@...r.kernel.org>
CC: Carlos Maiolino <cem@...nel.org>, Dave Chinner <david@...morbit.com>,
	"Darrick J . Wong" <djwong@...nel.org>, hch <hch@....de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Hans Holmberg
	<Hans.Holmberg@....com>
Subject: [RFC PATCH 0/2] Add mru cache for inode to zone allocation mapping

These patches cleans up the xfs mru code a bit and adds a cache for
keeping track of which zone an inode allocated data to last. Placing
file data in the same zone helps reduce write amplification.

Sending out as an RFC to get comments, specifically about the potential
mru lock contention when doing the lookup during allocation.

Can we do something better there?
I'll look into benchmarking the overhead, but any sugestions on how to
do this best would be helpful.

Christoph Hellwig (1):
  xfs: free the item in xfs_mru_cache_insert on failure

Hans Holmberg (1):
  xfs: add inode to zone caching for data placement

 fs/xfs/xfs_filestream.c |  15 ++----
 fs/xfs/xfs_mount.h      |   1 +
 fs/xfs/xfs_mru_cache.c  |  15 ++++--
 fs/xfs/xfs_zone_alloc.c | 109 ++++++++++++++++++++++++++++++++++++++++
 4 files changed, 126 insertions(+), 14 deletions(-)

-- 
2.34.1