From: Qu Wenruo <wqu@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 00/12] Renames and defrag cleanups
Date: Wed, 28 Aug 2024 08:32:28 +0930 [thread overview]
Message-ID: <49f29308-f177-4b42-852b-e0f6b28f5360@suse.com> (raw)
In-Reply-To: <cover.1724795623.git.dsterba@suse.com>
在 2024/8/28 07:25, David Sterba 写道:
> A few simple cleanups, dropping underscores and improving some code in
> defrag.
>
> David Sterba (12):
> btrfs: rename btrfs_submit_bio() to btrfs_submit_bbio()
> btrfs: rename __btrfs_submit_bio() and drop double underscores
> btrfs: rename __extent_writepage() and drop double underscores
> btrfs: rename __compare_inode_defrag() and drop double underscores
> btrfs: constify arguments of compare_inode_defrag()
> btrfs: rename __need_auto_defrag() and drop double underscores
> btrfs: rename __btrfs_add_inode_defrag() and drop double underscores
> btrfs: rename __btrfs_run_defrag_inode() and drop double underscores
> btrfs: clear defragmented inodes using postorder in
> btrfs_cleanup_defrag_inodes()
This one doesn't look safe to me as the rbtree_postorder_for_each_safe()
doesn't look like interruption safe.
The remaining ones looks good to me.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> btrfs: return void from btrfs_add_inode_defrag()
> btrfs: drop transaction parameter from btrfs_add_inode_defrag()
> btrfs: always pass readahead state to defrag
>
> fs/btrfs/bio.c | 20 +++----
> fs/btrfs/bio.h | 6 +--
> fs/btrfs/compression.c | 4 +-
> fs/btrfs/defrag.c | 100 ++++++++++++++---------------------
> fs/btrfs/defrag.h | 3 +-
> fs/btrfs/direct-io.c | 2 +-
> fs/btrfs/extent_io.c | 34 ++++++------
> fs/btrfs/inode.c | 8 +--
> fs/btrfs/scrub.c | 10 ++--
> fs/btrfs/subpage.c | 4 +-
> include/trace/events/btrfs.h | 2 +-
> 11 files changed, 86 insertions(+), 107 deletions(-)
>
prev parent reply other threads:[~2024-08-27 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 21:55 [PATCH 00/12] Renames and defrag cleanups David Sterba
2024-08-27 21:55 ` [PATCH 01/12] btrfs: rename btrfs_submit_bio() to btrfs_submit_bbio() David Sterba
2024-08-27 21:55 ` [PATCH 02/12] btrfs: rename __btrfs_submit_bio() and drop double underscores David Sterba
2024-08-27 21:55 ` [PATCH 03/12] btrfs: rename __extent_writepage() " David Sterba
2024-08-27 21:55 ` [PATCH 04/12] btrfs: rename __compare_inode_defrag() " David Sterba
2024-08-27 21:55 ` [PATCH 05/12] btrfs: constify arguments of compare_inode_defrag() David Sterba
2024-08-27 21:55 ` [PATCH 06/12] btrfs: rename __need_auto_defrag() and drop double underscores David Sterba
2024-08-27 21:55 ` [PATCH 07/12] btrfs: rename __btrfs_add_inode_defrag() " David Sterba
2024-08-27 21:55 ` [PATCH 08/12] btrfs: rename __btrfs_run_defrag_inode() " David Sterba
2024-08-27 21:55 ` [PATCH 09/12] btrfs: clear defragmented inodes using postorder in btrfs_cleanup_defrag_inodes() David Sterba
2024-08-27 22:59 ` Qu Wenruo
2024-08-27 23:18 ` David Sterba
2024-08-27 23:48 ` Qu Wenruo
2024-08-28 0:11 ` David Sterba
2024-08-28 0:13 ` Qu Wenruo
2024-08-27 21:55 ` [PATCH 10/12] btrfs: return void from btrfs_add_inode_defrag() David Sterba
2024-08-27 21:55 ` [PATCH 11/12] btrfs: drop transaction parameter " David Sterba
2024-08-27 21:55 ` [PATCH 12/12] btrfs: always pass readahead state to defrag David Sterba
2024-08-27 23:02 ` Qu Wenruo [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=49f29308-f177-4b42-852b-e0f6b28f5360@suse.com \
--to=wqu@suse.com \
--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