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 v8 2/3] btrfs: create read policy framework
Date: Wed, 21 Oct 2020 10:46:51 -0400 [thread overview]
Message-ID: <abc5a765-4327-c3e8-bc75-1868d8dd5345@toxicpanda.com> (raw)
In-Reply-To: <faf2c011057fab289535c3a84256272a23687097.1602756068.git.anand.jain@oracle.com>
On 10/20/20 10:02 AM, Anand Jain wrote:
> As of now, we use the %pid method to read striped mirrored data, which means
> process id determines the stripe id to read. This type of routing
> typically helps in a system with many small independent processes tying
> to read random data. On the other hand, the %pid based read IO policy is
> inefficient because if there is a single process trying to read a large
> file, the overall disk bandwidth remains under-utilized.
>
> So this patch introduces a read policy framework so that we could add more
> read policies, such as IO routing based on the device's wait-queue or manual
> when we have a read-preferred device or a policy based on the target
> storage caching.
>
> Signed-off-by: Anand Jain <anand.jain@oracle.com>
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
Thanks,
Josef
next prev parent reply other threads:[~2020-10-21 14:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 14:02 [PATCH v8 0/3] readmirror feature (read_policy sysfs and Anand Jain
2020-10-20 14:02 ` [PATCH v8 1/3] btrfs: add btrfs_strmatch helper Anand Jain
2020-10-21 14:44 ` Josef Bacik
2020-10-22 7:40 ` Anand Jain
2020-10-20 14:02 ` [PATCH v8 2/3] btrfs: create read policy framework Anand Jain
2020-10-21 14:46 ` Josef Bacik [this message]
2020-10-20 14:02 ` [PATCH v8 3/3] btrfs: create read policy sysfs attribute, pid Anand Jain
2020-10-21 14:42 ` Josef Bacik
2020-10-22 7:40 ` Anand Jain
2020-10-20 14:22 ` [PATCH v8 0/3] readmirror feature (read_policy sysfs and in-memory only approach) 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=abc5a765-4327-c3e8-bc75-1868d8dd5345@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