From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, linux-xfs@vger.kernel.org
Subject: Re: inode iterator cleanups
Date: Tue, 19 May 2020 08:40:17 +0200 [thread overview]
Message-ID: <20200519064017.GA24876@lst.de> (raw)
In-Reply-To: <20200519012337.GE17635@magnolia>
On Mon, May 18, 2020 at 06:23:37PM -0700, Darrick J. Wong wrote:
> On Mon, May 18, 2020 at 07:04:31PM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > this series cleans up a bunch of lose ends in the inode iterator
> > functions.
>
> Funny, I was going to send a series next cycle that refactors a fair
> amount of the incore inode iterators and then collapses the
> free_cowblocks/free_eofblocks code into a single worker and radix tree
> tag that takes care of all the speculative preallocation extent gc
> stuff...
>
> incore walks:
> https://lore.kernel.org/linux-xfs/157784075463.1360343.1278255546758019580.stgit@magnolia/
Except for the last few those seem non-brainers tat would could merge
ASAP..
The rest also doesn't look bad, so I'll happily defer this series.
OTOH the first on really should go in, either your or my version :)
next prev parent reply other threads:[~2020-05-19 6:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 17:04 inode iterator cleanups Christoph Hellwig
2020-05-18 17:04 ` [PATCH 1/6] xfs: remove xfs_inode_ag_iterator Christoph Hellwig
2020-05-18 17:04 ` [PATCH 2/6] xfs: mark xfs_inode_ag_iterator_tag static Christoph Hellwig
2020-05-18 17:04 ` [PATCH 3/6] xfs: remove __xfs_icache_free_eofblocks Christoph Hellwig
2020-05-18 17:04 ` [PATCH 4/6] xfs: merge xfs_inode_free_quota_{eof,cow}blocks Christoph Hellwig
2020-05-18 17:04 ` [PATCH 5/6] xfs: add a flags argument to xfs_icache_free_cowblocks Christoph Hellwig
2020-05-18 17:04 ` [PATCH 6/6] xfs: add a flags argument to xfs_icache_free_eofblocks Christoph Hellwig
2020-05-19 1:23 ` inode iterator cleanups Darrick J. Wong
2020-05-19 6:40 ` Christoph Hellwig [this message]
2020-05-20 1:45 ` Darrick J. Wong
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=20200519064017.GA24876@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--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