From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v6 0/3] btrfs: balance: improve kernel logs
Date: Tue, 20 Nov 2018 16:12:54 +0800 [thread overview]
Message-ID: <1542701577-24586-1-git-send-email-anand.jain@oracle.com> (raw)
v5->v6:
Mostly the defines non functional changes.
Use goto instead of return in middle of the define.
Pls ref individual patches 1/3 and 2/3 for more info.
v4->v5:
Mainly address David review comment [1].
[1]
https://patchwork.kernel.org/patch/10425987/
pls ref to individual patch 2/3 for details.
v3->v4:
Pls ref to individual patches.
Based on misc-next.
v2->v3:
Inspried by describe_relocation(), improves it, makes it a helper
function and use it to log the balance operations.
Kernel logs are very important for the forensic investigations of the
issues, these patchs make balance logs easy to review.
Anand Jain (3):
btrfs: add helper function describe_block_group()
btrfs: balance: add args info during start and resume
btrfs: balance: add kernel log for end or paused
fs/btrfs/relocation.c | 30 +------
fs/btrfs/volumes.c | 216 +++++++++++++++++++++++++++++++++++++++++++++++++-
fs/btrfs/volumes.h | 1 +
3 files changed, 217 insertions(+), 30 deletions(-)
--
1.8.3.1
next reply other threads:[~2018-11-20 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 8:12 Anand Jain [this message]
2018-11-20 8:12 ` [PATCH v6 1/3] btrfs: add helper function describe_block_group() Anand Jain
2018-11-20 8:12 ` [PATCH v6 2/3] btrfs: balance: add args info during start and resume Anand Jain
2018-11-20 8:12 ` [PATCH v6 3/3] btrfs: balance: add kernel log for end or paused Anand Jain
2018-11-20 14:48 ` [PATCH v6 0/3] btrfs: balance: improve kernel logs 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=1542701577-24586-1-git-send-email-anand.jain@oracle.com \
--to=anand.jain@oracle.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;
as well as URLs for NNTP newsgroup(s).