From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] device type and create chunk
Date: Tue, 18 Jan 2022 23:18:00 +0800 [thread overview]
Message-ID: <cover.1642518245.git.anand.jain@oracle.com> (raw)
I had these patches as part of experiments with the readpolicy I am
sending it now. This is different from the allocation_hint mode patch-set
where I use the device type to make the allocation destination automatic.
Patch 1/2 keeps the device's type in the struct btrfs_device so that we
could maintain the status if there are mixed devices in the
filesystem.
And if so, then patch 2/2 shall take care of arranging the disks by the
order of latency so that metadata chunks can pick disk with low latency
and data can pick the disk with higher latency.
By having fewer restrictions and not hard coding the chunk allocation
destination helps to cause the spillover to the available disk space
instead of causing the spurious ENOSPC.
Anand Jain (2):
btrfs: keep device type in the struct btrfs_device
btrfs: create chunk device type aware
fs/btrfs/dev-replace.c | 2 +
fs/btrfs/volumes.c | 90 ++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/volumes.h | 26 +++++++++++-
3 files changed, 117 insertions(+), 1 deletion(-)
--
2.33.1
next reply other threads:[~2022-01-18 15:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 15:18 Anand Jain [this message]
2022-01-18 15:18 ` [PATCH 1/2] btrfs: keep device type in the struct btrfs_device Anand Jain
2022-01-26 16:53 ` David Sterba
2022-01-29 16:24 ` Anand Jain
2022-02-01 17:06 ` David Sterba
2022-02-03 12:56 ` Anand Jain
2022-01-18 15:18 ` [PATCH 2/2] btrfs: create chunk device type aware Anand Jain
2022-01-26 17:01 ` David Sterba
2022-01-29 16:24 ` Anand Jain
2022-01-26 17:38 ` David Sterba
2022-01-29 16:46 ` Anand Jain
2022-01-30 22:15 ` Goffredo Baroncelli
2022-01-30 22:28 ` Goffredo Baroncelli
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=cover.1642518245.git.anand.jain@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).