From: Anand Jain <anand.jain@oracle.com>
To: waxhead@dirtcellar.net, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS subvolume RAID level
Date: Mon, 2 Dec 2019 18:48:07 +0800 [thread overview]
Message-ID: <ed65c577-3971-8c4f-c690-83e85dd8188e@oracle.com> (raw)
In-Reply-To: <494b0df1-2aab-5169-836d-e381498f64db@dirtcellar.net>
> I imagine that RAIDc4 for example could potentially give a grotesque
> speed increase for parallel read operations once BTRFS learns to
> distribute reads to the device with the least waitqueue / fastest devices.
That exactly was the objective of the Readmirror patch in the ML.
It proposed a framework to change the readmirror policy as needed.
Thanks, Anand
next prev parent reply other threads:[~2019-12-02 10:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 22:48 BTRFS subvolume RAID level waxhead
2019-11-29 0:44 ` Qu Wenruo
2019-12-02 10:48 ` Anand Jain [this message]
2019-12-02 23:27 ` waxhead
2019-12-03 1:30 ` Anand Jain
2019-12-03 20:31 ` waxhead
2019-12-05 12:10 ` 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=ed65c577-3971-8c4f-c690-83e85dd8188e@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=waxhead@dirtcellar.net \
/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).