From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, josef@toxicpanda.com,
btrfs-list@steev.me.uk
Subject: Re: [PATCH v4 0/2] readmirror feature (sysfs and in-memory only approach)
Date: Wed, 29 Jan 2020 19:07:53 +0100 [thread overview]
Message-ID: <20200129180752.GK3929@twin.jikos.cz> (raw)
In-Reply-To: <20200105151402.1440-1-anand.jain@oracle.com>
On Sun, Jan 05, 2020 at 11:14:00PM +0800, Anand Jain wrote:
> There were few RFCs [1] before, mainly to figure out storage
> (or in memory only) for the readmirror policy and the interface needed.
The persistent storage of the policy is not settled but adding the sysfs
value that's both read and write is safe enough so this patchset is in
the list of features for 5.7.
With the new raid1c34 profiles we'll need a better mirror selection to
utilize all the copies more effectively. Besides the default PID policy
we should have at least one more so it's not just the bare interface
without any real use.
prev parent reply other threads:[~2020-01-29 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 15:14 [PATCH v4 0/2] readmirror feature (sysfs and in-memory only approach) Anand Jain
2020-01-05 15:14 ` [PATCH 1/2] btrfs: add read_policy framework Anand Jain
2020-01-06 16:22 ` Josef Bacik
2020-01-29 18:26 ` David Sterba
2020-02-11 8:31 ` Anand Jain
2020-01-05 15:14 ` [PATCH 2/2] btrfs: sysfs, add read_policy attribute Anand Jain
2020-01-06 16:21 ` Josef Bacik
2020-01-07 4:52 ` [PATCH v2 " Anand Jain
2020-01-07 15:03 ` Josef Bacik
2020-01-07 15:25 ` Holger Hoffstätte
2020-01-08 4:16 ` [PATCH v3 " Anand Jain
2020-01-29 18:49 ` David Sterba
2020-02-12 14:24 ` Anand Jain
2020-01-29 18:07 ` David Sterba [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=20200129180752.GK3929@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=btrfs-list@steev.me.uk \
--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;
as well as URLs for NNTP newsgroup(s).