From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org
Cc: linux-xfs@vger.kernel.org, david@fromorbit.com
Subject: [PATCHSET v2 0/2] xfs: rename struct xfs_eofblocks
Date: Sun, 06 Jun 2021 10:54:24 -0700 [thread overview]
Message-ID: <162300206433.1202657.5753685964265403056.stgit@locust> (raw)
Hi all,
In the old days, struct xfs_eofblocks was an optional parameter to the
speculative post-EOF allocation garbage collector to narrow the scope of
a scan to files fitting specific criteria. Nowadays it is used for all
other kinds of inode cache walks (reclaim, quotaoff, inactivation), so
the name is no longer fitting. Change the flag namespace and rename the
structure to something more appropriate for what it does.
v2: separate the inode cache walk flag namespace from eofblocks
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=rename-eofblocks-5.14
---
fs/xfs/xfs_file.c | 8 +-
fs/xfs/xfs_icache.c | 178 ++++++++++++++++++++++++++-------------------------
fs/xfs/xfs_icache.h | 31 ++++++---
fs/xfs/xfs_ioctl.c | 41 +++++++-----
fs/xfs/xfs_trace.h | 36 +++++-----
5 files changed, 160 insertions(+), 134 deletions(-)
next reply other threads:[~2021-06-06 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 17:54 Darrick J. Wong [this message]
2021-06-06 17:54 ` [PATCH 1/2] xfs: change the prefix of XFS_EOF_FLAGS_* to XFS_ICWALK_FLAG_ Darrick J. Wong
2021-06-07 1:45 ` Dave Chinner
2021-06-07 10:59 ` Carlos Maiolino
2021-06-06 17:54 ` [PATCH 2/2] xfs: rename struct xfs_eofblocks to xfs_icwalk Darrick J. Wong
2021-06-07 1:47 ` Dave Chinner
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=162300206433.1202657.5753685964265403056.stgit@locust \
--to=djwong@kernel.org \
--cc=david@fromorbit.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 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.