From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org,
josef@toxicpanda.com, dsterba@suse.com
Subject: Re: [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach)
Date: Tue, 27 Oct 2020 19:02:34 +0100 [thread overview]
Message-ID: <20201027180233.GF6756@twin.jikos.cz> (raw)
In-Reply-To: <31c3da05-2238-da84-509e-3b29835ec33a@oracle.com>
On Tue, Oct 27, 2020 at 09:52:11AM +0800, Anand Jain wrote:
>
>
> On 24/10/20 1:04 am, David Sterba wrote:
> > On Thu, Oct 22, 2020 at 03:43:34PM +0800, Anand Jain wrote:
> >> v9: C coding style fixes in 1/3 and 3/3
> >
> > So the point of adding the sysfs knobs is to allow testing various
> > mirror selection strategies, what exactly was discussed in the past. Do
> > you have patches for that as well? It does not need to be final and
> > polished but at least give us something to test.
> >
>
> Sure. I just sent out the patchset [1]. It provides read_policy:
> latency, device, and round-robin.
>
> [1]
> https://patchwork.kernel.org/project/linux-btrfs/list/?series=371023
Exporting more information from the devices would help us to decide but
is there anything we can do just with what we have? Or eventually add
our counters like for the in-flight requests or total bytes. The
intention is not to duplicate what block layer does as we need to
experiment with the stats and heuristics it's just for that purpose and
we don't have to rely on other subsystem patches.
next prev parent reply other threads:[~2020-10-27 18:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 7:43 [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach) Anand Jain
2020-10-22 7:43 ` [PATCH v9 1/3] btrfs: add btrfs_strmatch helper Anand Jain
2020-10-23 11:12 ` Christoph Hellwig
2020-10-27 13:25 ` Anand Jain
2020-10-26 17:52 ` David Sterba
2020-10-27 13:19 ` Anand Jain
2020-10-27 18:00 ` David Sterba
2020-10-22 7:43 ` [PATCH v9 2/3] btrfs: create read policy framework Anand Jain
2020-10-22 7:43 ` [PATCH v9 3/3] btrfs: create read policy sysfs attribute, pid Anand Jain
2020-10-26 17:57 ` David Sterba
2020-10-28 12:37 ` Anand Jain
2020-10-23 17:04 ` [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach) David Sterba
2020-10-27 1:52 ` Anand Jain
2020-10-27 18:02 ` David Sterba [this message]
2020-10-28 12:06 ` Anand Jain
2020-10-26 14:01 ` Josef Bacik
2020-10-28 4:25 ` [PATCH v10 " Anand Jain
2020-10-28 4:25 ` [PATCH v10 1/3] btrfs: add btrfs_strmatch helper Anand Jain
2020-10-28 4:25 ` [PATCH v10 2/3] btrfs: create read policy framework Anand Jain
2020-10-28 4:25 ` [PATCH v10 3/3] btrfs: create read policy sysfs attribute, pid 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=20201027180233.GF6756@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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