From: Sun Yangkai <sunk67188@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>, linux-btrfs@vger.kernel.org
Cc: Boris Burkov <boris@bur.io>
Subject: Re: [PATCH 0/7] btrfs: fix periodic reclaim condition with some cleanup
Date: Sat, 3 Jan 2026 19:17:06 +0800 [thread overview]
Message-ID: <bf00ae7a-94ba-484e-9592-7eeab885f51a@gmail.com> (raw)
In-Reply-To: <27f36ff0-690f-4412-bc45-5ab6c55a68c7@gmx.com>
在 2026/1/2 05:14, Qu Wenruo 写道:
>
>
> 在 2026/1/1 22:24, Sun Yangkai 写道:
>>
>>
>> 在 2026/1/1 08:13, Qu Wenruo 写道:
>>>
>>>
>>> 在 2025/12/31 21:09, Sun YangKai 写道:
>>>> This series eliminates wasteful periodic reclaim operations that were occurring
>>>> when already failed to reclaim any new space, and includes several preparatory
>>>> cleanups.
>>>>
>>>> Patch 1-6 are non-functional changes.
>>>>
>>>> Patch 7 fixes the core issue, details are in the commit message.
>>>
>>> Fix first then cleanup please, this will make backport much easier.
>>>
>>> Thanks,
>>> Qu
>>
>> Sorry for bothering. I have no experience with backport things so I need some
>> more guidance here.
>>
>> The fix patch needs two of the cleanup patches applied.
>
> I didn't see anything in the cleanup that are significantly changing the behavior.
>
> Maybe some minor structure member or type change, but that's all.
>
> Your fix should still work use the older types/members, and that will make
> backport much easier, without the need to backport the cleanup as dependency.
>
>> I currently have no idea
>> what I could do to make backport easier. Should I also add "Fixes:" tag to the
>> two cleanup patch?
>
> Definitely no, and those cleanup should only be done after a fix.
>
> Cleanup is not a fix, thus they should not have such fixes tags.
>
>> Or should I squash the two cleanup and one fix together to
>> make a patch just for backport?
>
> No either.
>
> I did a quick simple reorder, and only minor changes needed to pass compile (not
> tested). The reordered fix is attached.
I've seen the patch. It will not work correctly but I've got the idea. I'll move
the fix patch in v2 patch set.
> Keep in mind that, during development you should focus on the fix first,
> ignoring all the unrelated minor problems, which should make your fix small and
> that's making it easier to backport.
Got it.
Thanks a lot :)
Sun YangKai
prev parent reply other threads:[~2026-01-03 11:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 10:39 [PATCH 0/7] btrfs: fix periodic reclaim condition with some cleanup Sun YangKai
2025-12-31 10:39 ` [PATCH 1/7] btrfs: change block group reclaim_mark to bool Sun YangKai
2025-12-31 10:39 ` [PATCH 2/7] btrfs: reorder btrfs_block_group members to reduce struct size Sun YangKai
2025-12-31 10:39 ` [PATCH 3/7] btrfs: use proper types for btrfs_block_group fields Sun YangKai
2025-12-31 10:39 ` [PATCH 4/7] btrfs: consolidate reclaim readiness checks in btrfs_should_reclaim() Sun YangKai
2025-12-31 10:39 ` [PATCH 5/7] btrfs: use u8 for reclaim threshold type Sun YangKai
2025-12-31 10:39 ` [PATCH 6/7] btrfs: clarify reclaim sweep control flow Sun YangKai
2025-12-31 10:39 ` [PATCH 7/7] btrfs: fix periodic reclaim condition Sun YangKai
2026-01-01 0:20 ` Qu Wenruo
2026-01-01 11:44 ` Sun Yangkai
2026-01-01 0:13 ` [PATCH 0/7] btrfs: fix periodic reclaim condition with some cleanup Qu Wenruo
2026-01-01 11:54 ` Sun Yangkai
2026-01-01 21:14 ` Qu Wenruo
2026-01-03 11:17 ` Sun Yangkai [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=bf00ae7a-94ba-484e-9592-7eeab885f51a@gmail.com \
--to=sunk67188@gmail.com \
--cc=boris@bur.io \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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