From: Josef Bacik <josef@toxicpanda.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com
Subject: Re: [PATCH v3 1/4] btrfs: add read_policy latency
Date: Tue, 19 Jan 2021 14:36:57 -0500 [thread overview]
Message-ID: <bf3eed32-6653-4151-85b6-1f249e601cf0@toxicpanda.com> (raw)
In-Reply-To: <64bb4905dc4b77e9fa22d8ba2635a36d15a33469.1610324448.git.anand.jain@oracle.com>
On 1/11/21 4:41 AM, Anand Jain wrote:
> The read policy type latency routes the read IO based on the historical
> average wait-time experienced by the read IOs through the individual
> device. This patch obtains the historical read IO stats from the kernel
> block layer and calculates its average.
>
> Example usage:
> echo "latency" > /sys/fs/btrfs/$uuid/read_policy
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> ---
> v3: The block layer commit 0d02129e76ed (block: merge struct block_device and
> struct hd_struct) has changed the first argument in the function
> part_stat_read_all() in 5.11-rc1. So the compilation will fail. This patch
> fixes it.
> Commit log updated.
>
> v2: Use btrfs_debug_rl() instead of btrfs_info_rl()
> It is better we have this debug until we test this on at least few
> hardwares.
> Drop the unrelated changes.
> Update change log.
>
> v1: Drop part_stat_read_all instead use part_stat_read
> Drop inflight
>
>
> fs/btrfs/sysfs.c | 3 ++-
> fs/btrfs/volumes.c | 38 ++++++++++++++++++++++++++++++++++++++
> fs/btrfs/volumes.h | 2 ++
> 3 files changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/sysfs.c b/fs/btrfs/sysfs.c
> index 19b9fffa2c9c..96ca7bef6357 100644
> --- a/fs/btrfs/sysfs.c
> +++ b/fs/btrfs/sysfs.c
> @@ -915,7 +915,8 @@ static bool strmatch(const char *buffer, const char *string)
> return false;
> }
>
> -static const char * const btrfs_read_policy_name[] = { "pid" };
> +/* Must follow the order as in enum btrfs_read_policy */
> +static const char * const btrfs_read_policy_name[] = { "pid", "latency" };
>
> static ssize_t btrfs_read_policy_show(struct kobject *kobj,
> struct kobj_attribute *a, char *buf)
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index f4037a6bd926..f7a0a83d2cd4 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -14,6 +14,7 @@
> #include <linux/semaphore.h>
> #include <linux/uuid.h>
> #include <linux/list_sort.h>
> +#include <linux/part_stat.h>
> #include "misc.h"
> #include "ctree.h"
> #include "extent_map.h"
> @@ -5490,6 +5491,39 @@ int btrfs_is_parity_mirror(struct btrfs_fs_info *fs_info, u64 logical, u64 len)
> return ret;
> }
>
> +static int btrfs_find_best_stripe(struct btrfs_fs_info *fs_info,
> + struct map_lookup *map, int first,
> + int num_stripe)
> +{
> + u64 est_wait = 0;
> + int best_stripe = 0;
> + int index;
> +
> + for (index = first; index < first + num_stripe; index++) {
> + u64 read_wait;
> + u64 avg_wait = 0;
> + unsigned long read_ios;
> + struct btrfs_device *device = map->stripes[index].dev;
> +
> + read_wait = part_stat_read(device->bdev, nsecs[READ]);
> + read_ios = part_stat_read(device->bdev, ios[READ]);
> +
> + if (read_wait && read_ios && read_wait >= read_ios)
> + avg_wait = div_u64(read_wait, read_ios);
> + else
> + btrfs_debug_rl(device->fs_devices->fs_info,
You can just use fs_info here, you already have it. I'm not in love with doing
this check every time, I'd rather cache the results somewhere. However if we're
read-only I can't think of a mechanism we could piggy back on, RW we could just
do it every transaction commit. Fix the fs_info thing and you can add
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2021-01-19 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 9:41 [PATCH v3 0/4] btrfs: read_policy types latency, device and round-robin Anand Jain
2021-01-11 9:41 ` [PATCH v3 1/4] btrfs: add read_policy latency Anand Jain
2021-01-19 19:36 ` Josef Bacik [this message]
2021-01-20 2:43 ` Anand Jain
2021-01-20 10:27 ` Michal Rostecki
2021-01-20 12:30 ` Anand Jain
2021-01-20 13:54 ` Michal Rostecki
2021-01-21 10:45 ` Anand Jain
2021-01-11 9:41 ` [PATCH v3 2/4] btrfs: introduce new device-state read_preferred Anand Jain
2021-01-19 19:44 ` Josef Bacik
2021-01-11 9:41 ` [PATCH v3 3/4] btrfs: introduce new read_policy device Anand Jain
2021-01-19 19:44 ` Josef Bacik
2021-01-11 9:41 ` [PATCH RFC 4/4] btrfs: introduce new read_policy round-robin Anand Jain
2021-01-19 19:41 ` Josef Bacik
2021-01-20 2:40 ` Anand Jain
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=bf3eed32-6653-4151-85b6-1f249e601cf0@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=anand.jain@oracle.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