public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: start deprecation of mount option inode_cache
Date: Tue, 7 Jul 2020 19:14:22 +0200	[thread overview]
Message-ID: <20200707171422.GD16141@twin.jikos.cz> (raw)
In-Reply-To: <20200623185032.14983-1-dsterba@suse.com>

On Tue, Jun 23, 2020 at 08:50:32PM +0200, David Sterba wrote:
> Remaining issues:
> 
> - if the option was enabled, new inodes created, the option disabled
>   again, the cache is still stored on the devices and there's currently
>   no way to remove it

The diffstat of the removal is

 b/fs/btrfs/Makefile           |    2 
 b/fs/btrfs/ctree.h            |    5 
 b/fs/btrfs/disk-io.c          |    2 
 b/fs/btrfs/free-space-cache.c |   88 ------
 b/fs/btrfs/inode.c            |   72 ++++-
 b/fs/btrfs/ioctl.c            |    1 
 b/fs/btrfs/relocation.c       |    1 
 b/fs/btrfs/super.c            |   10 
 b/fs/btrfs/transaction.c      |   16 -
 b/fs/btrfs/tree-log.c         |    2 
 fs/btrfs/inode-map.c          |  580 ------------------------------------------
 fs/btrfs/inode-map.h          |   16 -
 12 files changed, 72 insertions(+), 723 deletions(-)

whoever would like to claim it in the 5.11 develoment time will have to
provide fix for the remaining issue(s).

      parent reply	other threads:[~2020-07-07 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 18:50 [PATCH] btrfs: start deprecation of mount option inode_cache David Sterba
2020-06-23 23:27 ` Qu Wenruo
2020-06-24 11:00   ` David Sterba
2020-06-24 11:06     ` Qu Wenruo
2020-06-24  7:37 ` Steven Davies
2020-06-24  9:55   ` David Sterba
2020-07-07 17:14 ` David Sterba [this message]

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=20200707171422.GD16141@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@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