From: hch <hch@lst.de>
To: Hans Holmberg <Hans.Holmberg@wdc.com>
Cc: "linux-xfs@vger.kernel.org" <linux-xfs@vger.kernel.org>,
Carlos Maiolino <cem@kernel.org>,
Dave Chinner <david@fromorbit.com>,
"Darrick J . Wong" <djwong@kernel.org>, hch <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] Add mru cache for inode to zone allocation mapping
Date: Wed, 14 May 2025 15:00:14 +0200 [thread overview]
Message-ID: <20250514130014.GA20738@lst.de> (raw)
In-Reply-To: <20250514104937.15380-1-hans.holmberg@wdc.com>
On Wed, May 14, 2025 at 10:50:36AM +0000, Hans Holmberg wrote:
> While I was initially concerned by adding overhead to the allocation
> path, the cache actually reduces it as as we avoid going through the
> zone allocation algorithm for every random write.
>
> When I run a fio workload with 16 writers to different files in
> parallel, bs=8k, iodepth=4, size=1G, I get these throughputs:
>
> baseline with_cache
> 774 MB/s 858 MB/s (+11%)
>
> (averaged over three runs ech on a nullblk device)
>
> I see similar, figures when benchmarking on a zns nvme drive (+17%).
Very nice!
These should probably go into the commit message for patch 2 so they
are recorded. Carlos, is that something you can do when applying?
next prev parent reply other threads:[~2025-05-14 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:50 [PATCH 0/2] Add mru cache for inode to zone allocation mapping Hans Holmberg
2025-05-14 10:50 ` [PATCH 2/2] xfs: add inode to zone caching for data placement Hans Holmberg
2025-05-14 13:00 ` hch
2025-05-14 16:05 ` Darrick J. Wong
2025-05-14 10:50 ` [PATCH 1/2] xfs: free the item in xfs_mru_cache_insert on failure Hans Holmberg
2025-05-14 13:59 ` Carlos Maiolino
2025-05-14 16:04 ` Darrick J. Wong
2025-05-14 13:00 ` hch [this message]
2025-05-14 13:51 ` [PATCH 0/2] Add mru cache for inode to zone allocation mapping Carlos Maiolino
2025-05-14 13:55 ` hch
2025-05-14 13:52 ` Carlos Maiolino
2025-05-14 17:30 ` Carlos Maiolino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250514130014.GA20738@lst.de \
--to=hch@lst.de \
--cc=Hans.Holmberg@wdc.com \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.