From: David Sterba <dsterba@suse.cz>
To: Nikolay Borisov <nborisov@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] Remove deprecated inode cache feature
Date: Thu, 26 Nov 2020 16:31:35 +0100 [thread overview]
Message-ID: <20201126153135.GY6430@twin.jikos.cz> (raw)
In-Reply-To: <20201126131039.3441290-1-nborisov@suse.com>
On Thu, Nov 26, 2020 at 03:10:36PM +0200, Nikolay Borisov wrote:
> 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.
There's still the remaining issue what to do with the space occupied by
the cache inode if the feature was enabled. I haven't researched that,
eg. how big the inode is if it's worth removing it at all or if we
should do some lightweight scan to remove them at some appropriate time.
next prev parent reply other threads:[~2020-11-26 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 13:10 [PATCH 0/3] Remove deprecated inode cache feature Nikolay Borisov
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 ` David Sterba [this message]
2020-11-26 16:00 ` [PATCH 0/3] Remove deprecated " 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=20201126153135.GY6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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