All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/5] btrfs: defrag: don't waste CPU time on non-target extent
Date: Mon, 14 Feb 2022 17:40:11 +0100	[thread overview]
Message-ID: <20220214164011.GG12643@twin.jikos.cz> (raw)
In-Reply-To: <cover.1644561438.git.wqu@suse.com>

On Fri, Feb 11, 2022 at 02:41:38PM +0800, Qu Wenruo wrote:
> Changelog:
> v2:
> - Rebased to lastest misc-next
>   Just one small conflict with static_assert() update.
>   And this time only those patches are rebased to misc-next, thus it may
>   cause conflicts with fixes for defrag_check_next_extent() in the
>   future.
> 
> - Several grammar fixes
> 
> - Report accurate btrfs_defrag_ctrl::sectors_defragged
>   This is inspired by a comment from Filipe that the skip check
>   should be done in the defrag_collect_targets() call inside
>   defrag_one_range().
> 
>   This results a new patch in v2.
> 
> - Change the timing of btrfs_defrag_ctrl::last_scanned update
>   Now it's updated inside defrag_one_range(), which will give
>   us an accurate view, unlike the previous call site in
>   defrag_one_cluster().
> 
> - Don't change the timing of extent threshold.
> 
> - Rename @last_target to @last_is_target in defrag_collect_targets()
> 
> v3:
> - Add Reviewed-by tags
> 
> - Fix a wrong value in commit message of the 1st patch
> 
> - Make @orig_start const for the 3rd patch
> 
> - Fix a missing word "skip" in the 5th patch
> 
> - Remove one unnecessary assignment in the 5th patch
>   As we don't return the defragged sectors to user space.
> 
> v4:
> - Move the skip behavior before the btrfs_defrag_ctrl refactor
>   So it can be backported to v5.16

Thanks, I've picked the patch to misc-next. I'm not sure about the rest
because of the ctrl structure cleanup and there are still some pending
defrag fixes. So I'll add the remainig patches as topic branch for
testing.

  parent reply	other threads:[~2022-02-14 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  6:41 [PATCH v4 0/5] btrfs: defrag: don't waste CPU time on non-target extent Qu Wenruo
2022-02-11  6:41 ` [PATCH v4 1/5] btrfs: defrag: allow defrag_one_cluster() to skip large extent which is not a target Qu Wenruo
2022-02-11  6:41 ` [PATCH v4 2/5] btrfs: uapi: introduce BTRFS_DEFRAG_RANGE_MASK for later sanity check Qu Wenruo
2022-02-11  6:41 ` [PATCH v4 3/5] btrfs: defrag: introduce btrfs_defrag_ctrl structure for later usage Qu Wenruo
2022-02-11  6:41 ` [PATCH v4 4/5] btrfs: defrag: use btrfs_defrag_ctrl to replace btrfs_ioctl_defrag_range_args for btrfs_defrag_file() Qu Wenruo
2022-02-11  6:41 ` [PATCH v4 5/5] btrfs: defrag: make btrfs_defrag_file() to report accurate number of defragged sectors Qu Wenruo
2022-02-14 16:40 ` David Sterba [this message]
2022-02-15 15:45   ` [PATCH v4 0/5] btrfs: defrag: don't waste CPU time on non-target extent 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=20220214164011.GG12643@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@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 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.