From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Hans Holmberg <hans.holmberg@wdc.com>,
"Darrick J. Wong" <djwong@kernel.org>, Chris Mason <clm@meta.com>,
Keith Busch <kbusch@kernel.org>,
linux-xfs@vger.kernel.org
Subject: [PATCH 1/2] xfs: use a seprate member to track space availabe in the GC scatch buffer
Date: Tue, 27 Jan 2026 16:10:20 +0100 [thread overview]
Message-ID: <20260127151026.299341-2-hch@lst.de> (raw)
In-Reply-To: <20260127151026.299341-1-hch@lst.de>
When scratch_head wraps back to 0 and scratch_tail is also 0 because no
I/O has completed yet, the ring buffer could be mistaken for empty.
Fix this by introducing a separate scratch_available member in
struct xfs_zone_gc_data. This actually ends up simplifying the code as
well.
Reported-by: Chris Mason <clm@meta.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/xfs/xfs_zone_gc.c | 25 +++++++++----------------
1 file changed, 9 insertions(+), 16 deletions(-)
diff --git a/fs/xfs/xfs_zone_gc.c b/fs/xfs/xfs_zone_gc.c
index dfa6653210c7..8c08e5519bff 100644
--- a/fs/xfs/xfs_zone_gc.c
+++ b/fs/xfs/xfs_zone_gc.c
@@ -131,10 +131,13 @@ struct xfs_zone_gc_data {
/*
* Scratchpad to buffer GC data, organized as a ring buffer over
* discontiguous folios. scratch_head is where the buffer is filled,
- * and scratch_tail tracks the buffer space freed.
+ * scratch_tail tracks the buffer space freed, and scratch_available
+ * counts the space available in the ring buffer between the head and
+ * the tail.
*/
struct folio *scratch_folios[XFS_GC_NR_BUFS];
unsigned int scratch_size;
+ unsigned int scratch_available;
unsigned int scratch_head;
unsigned int scratch_tail;
@@ -212,6 +215,7 @@ xfs_zone_gc_data_alloc(
goto out_free_scratch;
}
data->scratch_size = XFS_GC_BUF_SIZE * XFS_GC_NR_BUFS;
+ data->scratch_available = data->scratch_size;
INIT_LIST_HEAD(&data->reading);
INIT_LIST_HEAD(&data->writing);
INIT_LIST_HEAD(&data->resetting);
@@ -574,18 +578,6 @@ xfs_zone_gc_ensure_target(
return oz;
}
-static unsigned int
-xfs_zone_gc_scratch_available(
- struct xfs_zone_gc_data *data)
-{
- if (!data->scratch_tail)
- return data->scratch_size - data->scratch_head;
-
- if (!data->scratch_head)
- return data->scratch_tail;
- return (data->scratch_size - data->scratch_head) + data->scratch_tail;
-}
-
static bool
xfs_zone_gc_space_available(
struct xfs_zone_gc_data *data)
@@ -596,7 +588,7 @@ xfs_zone_gc_space_available(
if (!oz)
return false;
return oz->oz_allocated < rtg_blocks(oz->oz_rtg) &&
- xfs_zone_gc_scratch_available(data);
+ data->scratch_available;
}
static void
@@ -625,8 +617,7 @@ xfs_zone_gc_alloc_blocks(
if (!oz)
return NULL;
- *count_fsb = min(*count_fsb,
- XFS_B_TO_FSB(mp, xfs_zone_gc_scratch_available(data)));
+ *count_fsb = min(*count_fsb, XFS_B_TO_FSB(mp, data->scratch_available));
/*
* Directly allocate GC blocks from the reserved pool.
@@ -730,6 +721,7 @@ xfs_zone_gc_start_chunk(
bio->bi_end_io = xfs_zone_gc_end_io;
xfs_zone_gc_add_data(chunk);
data->scratch_head = (data->scratch_head + len) % data->scratch_size;
+ data->scratch_available -= len;
WRITE_ONCE(chunk->state, XFS_GC_BIO_NEW);
list_add_tail(&chunk->entry, &data->reading);
@@ -862,6 +854,7 @@ xfs_zone_gc_finish_chunk(
data->scratch_tail =
(data->scratch_tail + chunk->len) % data->scratch_size;
+ data->scratch_available += chunk->len;
/*
* Cycle through the iolock and wait for direct I/O and layouts to
--
2.47.3
next prev parent reply other threads:[~2026-01-27 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 15:10 zone GC ringbuffer fix and cleanup Christoph Hellwig
2026-01-27 15:10 ` Christoph Hellwig [this message]
2026-01-28 5:35 ` [PATCH 1/2] xfs: use a seprate member to track space availabe in the GC scatch buffer Darrick J. Wong
2026-01-28 5:52 ` Christoph Hellwig
2026-01-28 5:56 ` Christoph Hellwig
2026-01-28 10:09 ` Carlos Maiolino
2026-01-28 12:00 ` Hans Holmberg
2026-01-29 11:32 ` Carlos Maiolino
2026-01-27 15:10 ` [PATCH 2/2] xfs: remove xfs_zone_gc_space_available Christoph Hellwig
2026-01-28 12:02 ` Hans Holmberg
2026-01-27 15:25 ` zone GC ringbuffer fix and cleanup Keith Busch
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=20260127151026.299341-2-hch@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=clm@meta.com \
--cc=djwong@kernel.org \
--cc=hans.holmberg@wdc.com \
--cc=kbusch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox