From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3 RESEND Rebased] readmirror feature
Date: Tue, 2 Jul 2019 16:09:30 +0800 [thread overview]
Message-ID: <5fcf9c23-89b5-b167-1f80-a0f4ac107d0b@oracle.com> (raw)
In-Reply-To: <20190626083402.1895-1-anand.jain@oracle.com>
Ping?
On 26/6/19 4:33 PM, Anand Jain wrote:
> These patches are tested to be working fine.
>
> Function call chain __btrfs_map_block()->find_live_mirror() uses
> thread pid to determine the %mirror_num when the mirror_num=0.
>
> This patch introduces a framework so that we can add policies to determine
> the %mirror_num. And adds the devid as the readmirror policy.
>
> The property is stored as an extented attributes of root inode
> (BTRFS_FS_TREE_OBJECTID).
> User provided devid list is validated against the fs_devices::dev_list.
>
> For example:
> Usage:
> btrfs property set <mnt> readmirror devid<n>[,<m>...]
> btrfs property set <mnt> readmirror ""
>
> mkfs.btrfs -fq -draid1 -mraid1 /dev/sd[b-d] && mount /dev/sdb /btrfs
> btrfs prop set /btrfs readmirror devid1,2
> btrfs prop get /btrfs readmirror
> readmirror=devid1,2
> getfattr -n btrfs.readmirror --absolute-names /btrfs
> btrfs.readmirror="devid1,2"
> btrfs prop set /btrfs readmirror ""
> getfattr -n btrfs.readmirror --absolute-names /btrfs
> /btrfs: btrfs.readmirror: No such attribute
> btrfs prop get /btrfs readmirror
>
> RFC->v1:
> Drops pid as one of the readmirror policy choices and as usual remains
> as default. And when the devid is reset the readmirror policy falls back
> to pid.
> Drops the mount -o readmirror idea, it can be added at a later point of
> time.
> Property now accepts more than 1 devid as readmirror device. As shown
> in the example above.
>
> Anand Jain (3):
> btrfs: add inode pointer to prop_handler::validate()
> btrfs: add readmirror property framework
> btrfs: add readmirror devid property
>
> fs/btrfs/props.c | 120 +++++++++++++++++++++++++++++++++++++++++++--
> fs/btrfs/props.h | 4 +-
> fs/btrfs/volumes.c | 25 +++++++++-
> fs/btrfs/volumes.h | 8 +++
> fs/btrfs/xattr.c | 2 +-
> 5 files changed, 150 insertions(+), 9 deletions(-)
>
next prev parent reply other threads:[~2019-07-02 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 8:33 [PATCH 0/3 RESEND Rebased] readmirror feature Anand Jain
2019-06-26 8:34 ` [PATCH 1/3 RESEND Rebased] btrfs: add inode pointer to prop_handler::validate() Anand Jain
2019-06-26 8:34 ` [PATCH 2/3 RESEND Rebased] btrfs: add readmirror property framework Anand Jain
2019-07-23 14:57 ` David Sterba
2019-07-24 2:42 ` Anand Jain
2019-06-26 8:34 ` [PATCH 3/3 RESEND Rebased] btrfs: add readmirror devid property Anand Jain
2019-07-23 14:55 ` David Sterba
2019-07-23 15:25 ` David Sterba
2019-06-26 8:37 ` [PATCH 1/2 RESEND Rebased] btrfs-progs: add helper to create xattr name Anand Jain
2019-06-26 8:37 ` [PATCH 2/2 RESEND Rebased] btrfs-progs: add readmirror policy Anand Jain
2019-07-23 13:53 ` David Sterba
2019-07-24 3:11 ` Anand Jain
2019-07-23 13:55 ` David Sterba
2019-07-02 8:09 ` Anand Jain [this message]
2019-07-24 0:20 ` [PATCH 0/3 RESEND Rebased] readmirror feature Qu Wenruo
2019-07-24 2:26 ` Anand Jain
2019-07-24 3:05 ` Qu Wenruo
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=5fcf9c23-89b5-b167-1f80-a0f4ac107d0b@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).