From: Christoph Hellwig <hch@infradead.org>
To: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
Cc: "Nirjhar Roy (IBM)" <nirjhar@linux.ibm.com>,
djwong@kernel.org, hch@infradead.org, cem@kernel.org,
david@fromorbit.com, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org, ritesh.list@gmail.com,
ojaswin@linux.ibm.com, hsiangkao@linux.alibaba.com
Subject: Re: [RFC v1 0/4] xfs: Add support to shrink multiple empty rtgroups
Date: Wed, 18 Mar 2026 08:20:12 -0700 [thread overview]
Message-ID: <abrCrFogLZ_MWTIb@infradead.org> (raw)
In-Reply-To: <0e20766d-5855-4514-a6bd-49e32261c162@gmail.com>
On Wed, Mar 18, 2026 at 08:13:28PM +0530, Nirjhar Roy (IBM) wrote:
> I am preparing a v2 incorporating all the initial review feedback received
> so far. In parallel, I am looking into adding shrinkfs support for zoned
> XFS - however, it would be great if we can discuss the current design and
> get a full review of the changes so far to get this work (shrinkfs for
> non-zoned realtime groups) into proper shape for the upcoming merge window
> first and submit zoned XFS shrinkfs support separately afterward. Do you
> think that make sense?
What is your plan for actually migrating data out of the to be shrunk
region, which is really the deal breaker to make this useful. Outside
of that zone support should be really trivial as it just means doing a
little less work.
next prev parent reply other threads:[~2026-03-18 15:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 5:57 xfs: Add support for multi rtgroup shrink+removal Nirjhar Roy (IBM)
2026-02-19 6:03 ` [RFC v1 0/4] xfs: Add support to shrink multiple empty rtgroups Nirjhar Roy (IBM)
2026-02-19 6:03 ` [RFC v1 1/4] xfs: Re-introduce xg_active_wq field in struct xfs_group Nirjhar Roy (IBM)
2026-02-19 6:13 ` Christoph Hellwig
2026-02-19 6:03 ` [RFC v1 2/4] xfs: Introduce xfs_rtginodes_ensure_all() Nirjhar Roy (IBM)
2026-02-19 6:15 ` Christoph Hellwig
2026-02-25 5:18 ` Nirjhar Roy (IBM)
2026-02-19 6:03 ` [RFC v1 3/4] xfs: Add a new state for shrinking Nirjhar Roy (IBM)
2026-02-19 6:03 ` [RFC v1 4/4] xfs: Add support to shrink multiple empty realtime groups Nirjhar Roy (IBM)
2026-02-19 6:23 ` Christoph Hellwig
2026-02-25 5:17 ` Nirjhar Roy (IBM)
2026-02-25 14:24 ` Christoph Hellwig
2026-02-26 12:59 ` Nirjhar Roy (IBM)
2026-02-23 11:29 ` [RFC v1 0/4] xfs: Add support to shrink multiple empty rtgroups Nirjhar Roy (IBM)
2026-03-18 14:43 ` Nirjhar Roy (IBM)
2026-03-18 15:20 ` Christoph Hellwig [this message]
2026-02-19 6:08 ` [PATCH v1] xfs_growfs: Allow shrink of realtime XFS Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 0/7] Add multi rtgroup grow and shrink tests Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 1/7] xfs: Introduce _require_realtime_xfs_{shrink,grow} pre-condition Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 2/7] xfs: Introduce helpers to count the number of bitmap and summary inodes Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 3/7] xfs: Add realtime group grow tests Nirjhar Roy (IBM)
2026-02-19 6:40 ` Christoph Hellwig
2026-02-25 5:24 ` Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 4/7] xfs: Add multi rt group grow + shutdown + recovery tests Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 5/7] xfs: Add realtime group shrink tests Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 6/7] xfs: Add multi rt group shrink + shutdown + recovery tests Nirjhar Roy (IBM)
2026-02-19 6:10 ` [PATCH v1 7/7] xfs: Add parallel back to back grow/shrink tests Nirjhar Roy (IBM)
2026-02-19 12:55 ` [PATCH v1 0/7] Add multi rtgroup grow and shrink tests Carlos Maiolino
2026-02-19 14:40 ` Nirjhar Roy (IBM)
2026-02-19 14:55 ` Carlos Maiolino
2026-02-19 15:49 ` Darrick J. Wong
2026-02-19 16:35 ` Carlos Maiolino
2026-02-20 11:24 ` Nirjhar Roy (IBM)
2026-02-20 16:10 ` Darrick J. Wong
2026-02-20 18:12 ` Nirjhar Roy (IBM)
2026-02-24 13:04 ` Carlos Maiolino
2026-02-20 11:20 ` Nirjhar Roy (IBM)
2026-02-20 16:15 ` Darrick J. Wong
2026-02-19 14:56 ` Andrey Albershteyn
2026-02-20 14:07 ` Konstantin Ryabitsev
2026-02-24 13:02 ` 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=abrCrFogLZ_MWTIb@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-xfs@vger.kernel.org \
--cc=nirjhar.roy.lists@gmail.com \
--cc=nirjhar@linux.ibm.com \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
/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