From: Sun YangKai <sunk67188@gmail.com>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix node balancing condition in balance_level()
Date: Thu, 07 Aug 2025 23:06:52 +0800 [thread overview]
Message-ID: <15559164.tv2OnDr8pf@saltykitkat> (raw)
In-Reply-To: <20250805184615.GD4088788@zen.localdomain>
Hi, Boris.
After working on node balance related code and fs_perf for days, I found that
current node balancing is not good enough with or without this patch. And I
come up with a different way to balance the nodes without adding much
complexity, which will takes me some days to implement and test it. I believe
it will be much better than the current one if I didn't mess things up.
BTW, I'm not familiar with fs benchmark, so I need some advice about how can I
get a reasonable benchmark result that can reflect the metadata operation
performance since I only have a 128G SSD can be used to benchmark, and it's
speed seems not stable enough. Currently I use kprobe to trace node balance
related functions to measure if the balance code works well.
Thanks,
Sun YangKai
prev parent reply other threads:[~2025-08-07 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 3:57 [PATCH] btrfs: fix node balancing condition in balance_level() Sun YangKai
2025-08-05 18:46 ` Boris Burkov
2025-08-06 6:07 ` Sun YangKai
2025-08-07 15:06 ` 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=15559164.tv2OnDr8pf@saltykitkat \
--to=sunk67188@gmail.com \
--cc=boris@bur.io \
--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