From: Nikolay Borisov <nborisov@suse.com>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, linux-btrfs@vger.kernel.org
Cc: Goldwyn Rodrigues <rgoldwyn@suse.com>
Subject: Re: [PATCH 3/3] btrfs: add more information for balance
Date: Wed, 5 Aug 2020 15:17:06 +0300 [thread overview]
Message-ID: <fd3307e1-eb59-26b0-790f-4845968e2bce@suse.com> (raw)
In-Reply-To: <20200803202913.15913-4-rgoldwyn@suse.de>
On 3.08.20 г. 23:29 ч., Goldwyn Rodrigues wrote:
> From: Goldwyn Rodrigues <rgoldwyn@suse.com>
>
> Include information about the state of the balance and expected,
> considered and completed statistics.
>
> Q: I am not sure of the cancelled state, and stopping seemed more
> appropriate since it was a transient state to cancelling the operation.
> Would you prefer to call it cancelled?
>
> This information is not used by user space as of now. We could use it
> for "btrfs balance status" or ignore this patch for inclusion at all.
>
> Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.com>
> ---
> fs/btrfs/sysfs.c | 29 ++++++++++++++++++++++++++++-
> 1 file changed, 28 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
> index 71950c121588..001a7ae375d0 100644
> --- a/fs/btrfs/sysfs.c
> +++ b/fs/btrfs/sysfs.c
> @@ -808,6 +808,33 @@ static ssize_t btrfs_checksum_show(struct kobject *kobj,
>
> BTRFS_ATTR(, checksum, btrfs_checksum_show);
>
> +static ssize_t btrfs_balance_show(struct btrfs_fs_info *fs_info, char *buf)
> +{
> + ssize_t ret = 0;
> + struct btrfs_balance_control *bctl;
> +
> + ret += scnprintf(buf, PAGE_SIZE, "balance\n");
> + spin_lock(&fs_info->balance_lock);
> + bctl = fs_info->balance_ctl;
> + if (!bctl) {
> + ret += scnprintf(buf + ret, PAGE_SIZE - ret,
> + "State: stopping\n");
nit: Shouldn't this be "stopped"?
> + goto out;
> + }
> + if (test_bit(BTRFS_FS_BALANCE_RUNNING, &fs_info->flags))
> + ret += scnprintf(buf + ret, PAGE_SIZE - ret,
> + "State: running\n");
> + else
> + ret += scnprintf(buf + ret, PAGE_SIZE - ret,
> + "State: paused\n");
> + ret += scnprintf(buf + ret, PAGE_SIZE - ret, "%llu %llu %llu\n",
> + bctl->stat.expected, bctl->stat.considered,
> + bctl->stat.completed);
> +out:
> + spin_unlock(&fs_info->balance_lock);
> + return ret;
> +}
Technically I don't see anything wrong with this, however I got reminded
of the following text from sysfs documentation:
"
Mixing types, expressing multiple lines of data, and doing fancy
formatting of data is heavily frowned upon. Doing these things may get
you publicly humiliated and your code rewritten without notice.
"
> +
> static ssize_t btrfs_exclusive_operation_show(struct kobject *kobj,
> struct kobj_attribute *a, char *buf)
> {
> @@ -816,7 +843,7 @@ static ssize_t btrfs_exclusive_operation_show(struct kobject *kobj,
> case BTRFS_EXCLOP_NONE:
> return scnprintf(buf, PAGE_SIZE, "none\n");
> case BTRFS_EXCLOP_BALANCE:
> - return scnprintf(buf, PAGE_SIZE, "balance\n");
> + return btrfs_balance_show(fs_info, buf);
> case BTRFS_EXCLOP_DEV_ADD:
> return scnprintf(buf, PAGE_SIZE, "device add\n");
> case BTRFS_EXCLOP_DEV_REPLACE:
>
next prev parent reply other threads:[~2020-08-05 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 20:29 [PATCH v2 0/3] btrfs: Enumerate and export exclusive operations Goldwyn Rodrigues
2020-08-03 20:29 ` [PATCH 1/3] btrfs: enumerate the type of exclusive operation in progress Goldwyn Rodrigues
2020-08-05 8:35 ` Nikolay Borisov
2020-08-03 20:29 ` [PATCH 2/3] btrfs: export currently executing exclusive operation via sysfs Goldwyn Rodrigues
2020-08-05 9:04 ` Nikolay Borisov
2020-08-03 20:29 ` [PATCH 3/3] btrfs: add more information for balance Goldwyn Rodrigues
2020-08-05 12:17 ` Nikolay Borisov [this message]
2020-08-05 16:29 ` Goldwyn Rodrigues
2020-08-03 20:30 ` [PATCH 1/4] btrfs-progs: get_fsid_fd() for getting fsid using fd Goldwyn Rodrigues
2020-08-03 20:30 ` [PATCH 2/4] btrfs-progs: add sysfs file reading functions Goldwyn Rodrigues
2020-08-03 20:30 ` [PATCH 3/4] btrfs-progs: Check for exclusive operation before issuing ioctl Goldwyn Rodrigues
2020-08-03 20:30 ` [PATCH 4/4] btrfs-progs: Enqueue command if it can't be performed immediately Goldwyn Rodrigues
-- strict thread matches above, loose matches on Subject: below --
2020-07-27 22:04 [PATCH 0/3] btrfs: Enumerate and export exclusive operations Goldwyn Rodrigues
2020-07-27 22:04 ` [PATCH 3/3] btrfs: add more information for balance Goldwyn Rodrigues
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=fd3307e1-eb59-26b0-790f-4845968e2bce@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rgoldwyn@suse.com \
--cc=rgoldwyn@suse.de \
/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