From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
Chandan Babu R <chandan.babu@oracle.com>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH 8/9] xfs: stop the steal (of data blocks for RT indirect blocks)
Date: Tue, 20 Feb 2024 06:13:41 +0100 [thread overview]
Message-ID: <20240220051341.GB5988@lst.de> (raw)
In-Reply-To: <ZdPogLjdypKDgm0D@dread.disaster.area>
On Tue, Feb 20, 2024 at 10:47:12AM +1100, Dave Chinner wrote:
> Ok. If you delay the ip->i_delayed_blks and quota accounting until
> after the incore extent tree updates are done, this code doesn't
> need to undo anything and can just return an error. We should also
> keep in mind that an error here will likely cause a filesystem
> shutdown when the transaction is canceled....
Yes. However (as documented in the commit log), the only place where
I think it can actually happen is on a buffered write errors as "real"
hole punches always flush delalloc space before.
> FWIW, if we are going to do this for rt, we should probably also
> consider do it for normal delalloc conversion when the indlen
> reservation runs out due to excessive fragmentation of large
> extents. Separate patch and all that, but it doesn't really make
> sense to me to only do this for RT when we know it is also needed in
> reare cases on non-rt workloads...
Can it happen for non-RT extents? That would assume the required new
indirect block reservation for splitting an extent would have to be
larger than the amount we punch out.
next prev parent reply other threads:[~2024-02-20 5:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 6:34 bring back RT delalloc support Christoph Hellwig
2024-02-19 6:34 ` [PATCH 1/9] xfs: make XFS_TRANS_LOWMODE match the other XFS_TRANS_ definitions Christoph Hellwig
2024-02-19 6:34 ` [PATCH 2/9] xfs: move RT inode locking out of __xfs_bunmapi Christoph Hellwig
2024-02-19 23:55 ` Dave Chinner
2024-02-20 5:10 ` Christoph Hellwig
2024-02-19 6:34 ` [PATCH 3/9] xfs: split xfs_mod_freecounter Christoph Hellwig
2024-02-19 23:21 ` Dave Chinner
2024-02-20 7:28 ` Christoph Hellwig
2024-02-20 16:08 ` Christoph Hellwig
2024-02-21 0:00 ` Dave Chinner
2024-02-19 6:34 ` [PATCH 4/9] xfs: reinstate RT support in xfs_bmapi_reserve_delalloc Christoph Hellwig
2024-02-19 6:34 ` [PATCH 5/9] xfs: cleanup fdblock/frextent accounting in xfs_bmap_del_extent_delay Christoph Hellwig
2024-02-19 6:34 ` [PATCH 6/9] xfs: support RT inodes in xfs_mod_delalloc Christoph Hellwig
2024-02-19 23:30 ` Dave Chinner
2024-02-20 5:14 ` Christoph Hellwig
2024-02-19 6:34 ` [PATCH 7/9] xfs: look at m_frextents in xfs_iomap_prealloc_size for RT allocations Christoph Hellwig
2024-02-19 6:34 ` [PATCH 8/9] xfs: stop the steal (of data blocks for RT indirect blocks) Christoph Hellwig
2024-02-19 23:47 ` Dave Chinner
2024-02-20 5:13 ` Christoph Hellwig [this message]
2024-02-19 6:34 ` [PATCH 9/9] xfs: reinstate delalloc for RT inodes (if sb_rextsize == 1) Christoph Hellwig
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=20240220051341.GB5988@lst.de \
--to=hch@lst.de \
--cc=chandan.babu@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@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