Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Su Yue <suy.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 05/17] btrfs-progs: lowmem check: introduce modify_block_groups_cache()
Date: Wed, 20 Dec 2017 13:38:55 +0800	[thread overview]
Message-ID: <2bd256bd-319e-5947-13fc-d52babbba300@gmx.com> (raw)
In-Reply-To: <20171220045731.19343-6-suy.fnst@cn.fujitsu.com>


[-- Attachment #1.1: Type: text/plain, Size: 3899 bytes --]



On 2017年12月20日 12:57, Su Yue wrote:
> Excluding or pining all metadata blocks is not time-efficient for large
> storage filesystems.
> Here is another way to mark all metadata block groups full and allocate
> a new chunk for CoW. So new reservered extents never overwrite
> extents.
> 
> Introduce modify_block_groups_cache() to modify all blocks groups
> cache state and set all extents in block groups unfree in free space
> cache.
> 
> Suggested-by: Qu Wenruo <wqu@suse.com>
> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
> ---
>  cmds-check.c | 83 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 83 insertions(+)
> 
> diff --git a/cmds-check.c b/cmds-check.c
> index dd46569f3811..d98d4bda7357 100644
> --- a/cmds-check.c
> +++ b/cmds-check.c
> @@ -10828,6 +10828,89 @@ static void reset_cached_block_groups(struct btrfs_fs_info *fs_info)
>  	}
>  }
>  
> +/*
> + * Mark all extents unfree in the block group. And set @block_group->cached
> + * according to @cache.
> + */
> +static int modify_block_group_cache(struct btrfs_fs_info *fs_info,
> +		    struct btrfs_block_group_cache *block_group, int cache)
> +{
> +	struct extent_io_tree *free_space_cache = &fs_info->free_space_cache;
> +	u64 start = block_group->key.objectid;
> +	u64 end = start + block_group->key.offset;
> +
> +	if (cache && !block_group->cached) {
> +		block_group->cached = 1;
> +		clear_extent_dirty(free_space_cache, start, end - 1);
> +	}
> +
> +	if (!cache && block_group->cached) {
> +		block_group->cached = 0;
> +		clear_extent_dirty(free_space_cache, start, end - 1);
> +	}
> +	return 0;
> +}
> +
> +/*
> + * Modify block groups which have @flags unfree in free space cache.
> + *
> + * @cache: if 0, clear block groups cache state;
> + *         not 0, mark blocks groups cached.

The naming of the function and the @cache parameter is quite confusing.

And so is the later usage of the function.
It's used by both marking all block groups full and revert the full mark
as cleanup.


I would call the function mark_block_groups_full() to do the full
marking thing, without the extra @cache parameter.

And another function to clear_block_groups_full() to make them into back
to normal status.

Thanks,
Qu
> + */
> +static int modify_block_groups_cache(struct btrfs_fs_info *fs_info, u64 flags,
> +				     int cache)
> +{
> +	struct btrfs_root *root = fs_info->extent_root;
> +	struct btrfs_key key;
> +	struct btrfs_path path;
> +	struct btrfs_block_group_cache *bg_cache;
> +	struct btrfs_block_group_item *bi;
> +	struct btrfs_block_group_item bg_item;
> +	struct extent_buffer *eb;
> +	int slot;
> +	int ret;
> +
> +	key.objectid = 0;
> +	key.type = BTRFS_BLOCK_GROUP_ITEM_KEY;
> +	key.offset = 0;
> +
> +	btrfs_init_path(&path);
> +	ret = btrfs_search_slot(NULL, root, &key, &path, 0, 0);
> +	if (ret < 0) {
> +		error("fail to search block groups due to %s", strerror(-ret));
> +		goto out;
> +	}
> +
> +	while (1) {
> +		eb = path.nodes[0];
> +		slot = path.slots[0];
> +		btrfs_item_key_to_cpu(eb, &key, slot);
> +		bg_cache = btrfs_lookup_block_group(fs_info, key.objectid);
> +		if (!bg_cache) {
> +			ret = -ENOENT;
> +			goto out;
> +		}
> +
> +		bi = btrfs_item_ptr(eb, slot, struct btrfs_block_group_item);
> +		read_extent_buffer(eb, &bg_item, (unsigned long)bi,
> +				   sizeof(bg_item));
> +		if (btrfs_block_group_flags(&bg_item) & flags)
> +			modify_block_group_cache(fs_info, bg_cache, cache);
> +
> +		ret = btrfs_next_item(root, &path);
> +		if (ret > 0) {
> +			ret = 0;
> +			goto out;
> +		}
> +		if (ret < 0)
> +			goto out;
> +	}
> +
> +out:
> +	btrfs_release_path(&path);
> +	return ret;
> +}
> +
>  static int check_extent_refs(struct btrfs_root *root,
>  			     struct cache_tree *extent_cache)
>  {
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]

  reply	other threads:[~2017-12-20  5:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20  4:57 [PATCH v2 00/17] btrfs-progs: lowmem check: avoid extents overwrite Su Yue
2017-12-20  4:57 ` [PATCH v2 01/17] btrfs-progs: lowmem check: release path in repair_extent_data_item() Su Yue
2017-12-20  4:57 ` [PATCH v2 02/17] btrfs-progs: lowmem check: record returned errors after walk_down_tree_v2() Su Yue
2017-12-29 11:17   ` Nikolay Borisov
2018-01-02  1:44     ` Su Yue
2018-01-02  1:50     ` Su Yue
2017-12-20  4:57 ` [PATCH v2 03/17] btrfs-progs: lowmem check: assign @parent early in repair_extent_data_item() Su Yue
2017-12-20  4:57 ` [PATCH v2 04/17] btrfs-progs: lowmem check: exclude extents of metadata blocks Su Yue
2017-12-20  4:57 ` [PATCH v2 05/17] btrfs-progs: lowmem check: introduce modify_block_groups_cache() Su Yue
2017-12-20  5:38   ` Qu Wenruo [this message]
2017-12-20  4:57 ` [PATCH v2 06/17] btrfs-progs: lowmem check: introduce force_cow_in_new_chunk() Su Yue
2017-12-20  5:41   ` Qu Wenruo
2017-12-20  8:21     ` Su Yue
2017-12-20  8:37       ` Qu Wenruo
2017-12-21  6:51         ` Qu Wenruo
2017-12-21  7:06           ` Su Yue
2017-12-21  7:09           ` Su Yue
2017-12-21  7:12             ` Qu Wenruo
2017-12-26  8:17               ` Su Yue
2017-12-26 10:28                 ` Qu Wenruo
2017-12-27  1:11                   ` Su Yue
2018-01-09  7:44                     ` Qu Wenruo
2017-12-20  4:57 ` [PATCH v2 07/17] btrfs-progs: lowmem check: introduce try_avoid_extents_overwrite() Su Yue
2017-12-20  5:46   ` Qu Wenruo
2017-12-20  4:57 ` [PATCH v2 08/17] btrfs-progs: lowmem check: exclude extents if init-extent-tree in lowmem Su Yue
2017-12-20  4:57 ` [PATCH v2 09/17] btrfs-progs: lowmem check: start to remove parameters @trans " Su Yue
2017-12-20  5:51   ` Qu Wenruo
2017-12-20  4:57 ` [PATCH v2 10/17] btrfs-progs: lowmem check: remove parameter @trans of delete_extent_item() Su Yue
2017-12-20  4:57 ` [PATCH v2 11/17] btrfs-progs: lowmem check: remove parameter @trans of repair_chunk_item() Su Yue
2017-12-20  4:57 ` [PATCH v2 12/17] btrfs-progs: lowmem check: remove parameter @trans of repair_extent_item() Su Yue
2017-12-20  4:57 ` [PATCH v2 13/17] btrfs-progs: lowmem check: remove parameter @trans of check_leaf_items() Su Yue
2017-12-20  4:57 ` [PATCH v2 14/17] btrfs-progs: lowmem check: remove parameter @trans of repair_tree_back_ref() Su Yue
2017-12-20  4:57 ` [PATCH v2 15/17] btrfs-progs: lowmem check: remove parameter @trans of check_btrfs_root() Su Yue
2017-12-20  4:57 ` [PATCH v2 16/17] btrfs-progs: lowmem check: introduce repair_block_accounting() Su Yue
2017-12-20  4:57 ` [PATCH v2 17/17] btrfs-progs: lowmem check: end of removing parameters @trans in lowmem Su Yue
2017-12-20  5:59 ` [PATCH v2 00/17] btrfs-progs: lowmem check: avoid extents overwrite Qu Wenruo

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=2bd256bd-319e-5947-13fc-d52babbba300@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=suy.fnst@cn.fujitsu.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