From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: Nikolay Borisov <nborisov@suse.com>
Subject: [PATCH 0/3] Remove deprecated inode cache feature
Date: Thu, 26 Nov 2020 15:10:36 +0200 [thread overview]
Message-ID: <20201126131039.3441290-1-nborisov@suse.com> (raw)
This patchset removes inode cache feature which has been deprecated since kernel
v5.9 release. First 2 patches move code around and replace calls of functions
which are to be removed. Patch 3 finally removes inode cache for good.
I tested this under xfstest and didn't observe any new regressions.
Nikolay Borisov (3):
btrfs: Move btrfs_find_highest_objectid/btrfs_find_free_objectid to
disk-io.c
btrfs: Replace calls to btrfs_find_free_ino with
btrfs_find_free_objectid
btrfs: Remove inode cache feature
fs/btrfs/Makefile | 2 +-
fs/btrfs/ctree.h | 15 +-
fs/btrfs/disk-io.c | 78 +++--
fs/btrfs/disk-io.h | 2 +
fs/btrfs/free-space-cache.c | 177 -----------
fs/btrfs/free-space-cache.h | 6 -
fs/btrfs/inode-map.c | 582 ------------------------------------
fs/btrfs/inode-map.h | 16 -
fs/btrfs/inode.c | 23 +-
fs/btrfs/ioctl.c | 1 -
fs/btrfs/relocation.c | 1 -
fs/btrfs/super.c | 8 -
fs/btrfs/transaction.c | 19 --
fs/btrfs/tree-log.c | 1 -
14 files changed, 66 insertions(+), 865 deletions(-)
delete mode 100644 fs/btrfs/inode-map.c
delete mode 100644 fs/btrfs/inode-map.h
--
2.25.1
next reply other threads:[~2020-11-26 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:10 Nikolay Borisov [this message]
2020-11-26 13:10 ` [PATCH 1/3] btrfs: Move btrfs_find_highest_objectid/btrfs_find_free_objectid to disk-io.c Nikolay Borisov
2020-11-26 13:10 ` [PATCH 2/3] btrfs: Replace calls to btrfs_find_free_ino with btrfs_find_free_objectid Nikolay Borisov
2020-11-26 13:10 ` [PATCH 3/3] btrfs: Remove inode cache feature Nikolay Borisov
2020-11-27 16:30 ` David Sterba
2020-11-26 15:31 ` [PATCH 0/3] Remove deprecated " David Sterba
2020-11-26 16:00 ` Nikolay Borisov
2020-11-27 14:58 ` David Sterba
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=20201126131039.3441290-1-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@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