From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH 0/5] Refactor gfs2_evict_inode
Date: Tue, 15 Sep 2020 09:38:17 -0500 [thread overview]
Message-ID: <20200915143822.16485-1-rpeterso@redhat.com> (raw)
Function gfs2_evict_inode is very large and messy. This patch set is an
attempt to simplify the function and make it more understandable. This
will make it easier to maintain. I did this mainly because we need to fix
it so it can call truncate_inode_pages on the inode glock's address space.
Bob Peterson (5):
gfs2: switch variable error to ret in gfs2_evict_inode
gfs2: factor delete_evicted_inode out of gfs2_evict_inode
gfs2: further simplify gfs2_evict_inode with new func
may_delete_evicted
gfs2: factor out evict code related to dinodes we are not deleting
gfs2: simplify the logic in gfs2_evict_inode
fs/gfs2/super.c | 214 ++++++++++++++++++++++++++++++------------------
1 file changed, 136 insertions(+), 78 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-15 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 14:38 Bob Peterson [this message]
2020-09-15 14:38 ` [Cluster-devel] [GFS2 PATCH 1/5] gfs2: switch variable error to ret in gfs2_evict_inode Bob Peterson
2020-09-15 14:38 ` [Cluster-devel] [GFS2 PATCH 2/5] gfs2: factor delete_evicted_inode out of gfs2_evict_inode Bob Peterson
2020-09-15 19:08 ` Andreas Gruenbacher
2020-09-15 14:38 ` [Cluster-devel] [GFS2 PATCH 3/5] gfs2: further simplify gfs2_evict_inode with new func may_delete_evicted Bob Peterson
2020-09-15 19:09 ` Andreas Gruenbacher
2020-09-15 14:38 ` [Cluster-devel] [GFS2 PATCH 4/5] gfs2: factor out evict code related to dinodes we are not deleting Bob Peterson
2020-09-15 19:09 ` Andreas Gruenbacher
2020-09-15 14:38 ` [Cluster-devel] [GFS2 PATCH 5/5] gfs2: simplify the logic in gfs2_evict_inode Bob Peterson
2020-09-15 19:08 ` [Cluster-devel] [GFS2 PATCH 0/5] Refactor gfs2_evict_inode Andreas Gruenbacher
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=20200915143822.16485-1-rpeterso@redhat.com \
--to=rpeterso@redhat.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;
as well as URLs for NNTP newsgroup(s).