All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Josef Bacik <josef@toxicpanda.com>
Cc: David Sterba <dsterba@suse.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Pankaj Raghav <p.raghav@samsung.com>
Subject: Re: [PATCH 2/5] btrfs: allow block group background reclaim for !zoned fs'es
Date: Tue, 22 Mar 2022 17:40:45 +0000	[thread overview]
Message-ID: <PH0PR04MB74163203C0988A3C4751BCC59B179@PH0PR04MB7416.namprd04.prod.outlook.com> (raw)
In-Reply-To: YjoJgS244Y9x6OPu@localhost.localdomain

On 22/03/2022 18:38, Josef Bacik wrote:
>> +static inline bool should_reclaim_block_group(struct btrfs_block_group *block_group,
>> +					      u64 bytes_freed)
>> +{
>> +	const struct btrfs_space_info *space_info = block_group->space_info;
>> +	const int reclaim_thresh = READ_ONCE(space_info->bg_reclaim_threshold);
>> +	const u64 new_val = block_group->used;
>> +	const u64 old_val = new_val + bytes_freed;
>> +	u64 thresh;
>> +
> 
> Actually do we want to do a
> 
> if (btrfs_zoned())
> 	return false;
> 
> here and leave the auto reclaim zoned behavior the way it is?  Or do you want to
> delete your stuff and rely on this as the way that we setup zoned block groups
> for relocation?  If we use this then you could make the
> fs_info->bg_reclaim_threshold also apply here.  Thanks,
> 
>

I actually like the per-space info knob for the individual block groups and then
the global one to kick in reclaim.

  reply	other threads:[~2022-03-22 17:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 16:14 [PATCH 0/5] btrfs: rework background block group relocation Johannes Thumshirn
2022-03-21 16:14 ` [PATCH 1/5] btrfs: make the bg_reclaim_threshold per-space info Johannes Thumshirn
2022-03-22 17:32   ` Josef Bacik
2022-03-22 17:34     ` Johannes Thumshirn
2022-03-21 16:14 ` [PATCH 2/5] btrfs: allow block group background reclaim for !zoned fs'es Johannes Thumshirn
2022-03-22 17:38   ` Josef Bacik
2022-03-22 17:40     ` Johannes Thumshirn [this message]
2022-03-21 16:14 ` [PATCH 3/5] btrfs: change the bg_reclaim_threshold valid region from 0 to 100 Johannes Thumshirn
2022-03-21 16:14 ` [PATCH 4/5] btrfs: make calc_available_free_space available outside of space-info Johannes Thumshirn
2022-03-22 17:34   ` Josef Bacik
2022-03-21 16:14 ` [PATCH 5/5] btrfs: zoned: make auto-reclaim less aggressive Johannes Thumshirn
2022-03-23  9:08   ` Pankaj Raghav
2022-03-23  9:11     ` Johannes Thumshirn
2022-03-23  9:14       ` Pankaj Raghav
2022-03-23 10:39         ` Johannes Thumshirn
2022-03-23 11:24           ` Pankaj Raghav
2022-03-23 11:52             ` Johannes Thumshirn
2022-03-23 19:37               ` Pankaj Raghav
2022-03-24  0:06               ` Damien Le Moal

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=PH0PR04MB74163203C0988A3C4751BCC59B179@PH0PR04MB7416.namprd04.prod.outlook.com \
    --to=johannes.thumshirn@wdc.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=p.raghav@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.