From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: "Ellis H. Wilson III" <ellisw@panasas.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Metadata / Data on Heterogeneous Media
Date: Fri, 16 Feb 2018 11:57:13 +0800 [thread overview]
Message-ID: <50dba73c-9b0b-636f-f44a-224cf355f6aa@gmx.com> (raw)
In-Reply-To: <1b2df382-0402-a806-9ebf-996fabf22ba4@panasas.com>
[-- Attachment #1.1: Type: text/plain, Size: 2196 bytes --]
On 2018年02月16日 01:15, Ellis H. Wilson III wrote:
> In discussing the performance of various metadata operations over the
> past few days I've had this idea in the back of my head, and wanted to
> see if anybody had already thought about it before (likely, I would guess).
>
> It appears based on this page:
> https://btrfs.wiki.kernel.org/index.php/Btrfs_design
> that data and metadata in BTRFS are fairly well isolated from one
> another, particularly in the case of large files. This appears
> reinforced by a recent comment from Qu ("...btrfs strictly
> split metadata and data usage...").
>
> Yet, while there are plenty of options to RAID0/1/10/etc across
> generally homogeneous media types, there doesn't appear to be any
> functionality (at least that I can find) to segment different BTRFS
> internals to different types of devices. E.G., place metadata trees and
> extent block groups on SSD, and data trees and extent block groups on
> HDD(s).
Just want to point out that, metadata trees, block groups, *AND* tree
blocks of file trees (data trees in your words) are all *METADATA*.
That's to say, btrfs can't isolate tree blocks from file trees and other
trees. They are all tree blocks, thus all metadata.
Real data is, non-inlined, non-hole data. Tree blocks of file tress has
pointers to data, but the tree blocks of file trees are still metadata.
So even on day, btrfs supports to alloc data/meta chunks using different
strategy, we are still a step away from your
different-chunk-for-different-tree idea.
Thanks,
Qu
>
> Is this something that has already been considered (and if so,
> implemented, which would make me extremely happy)? Is it feasible it is
> hasn't been approached yet? I admit my internal knowledge of BTRFS is
> fleeting, though I'm trying to work on that daily at this time, so
> forgive me if this is unapproachable for obvious architectural reasons.
>
> Best,
>
> ellis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
prev parent reply other threads:[~2018-02-16 3:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 17:15 Metadata / Data on Heterogeneous Media Ellis H. Wilson III
2018-02-15 19:06 ` Adam Borowski
2018-02-15 20:30 ` Ellis H. Wilson III
2018-02-15 19:11 ` Hugo Mills
2018-02-15 20:31 ` Ellis H. Wilson III
2018-02-16 3:57 ` Qu Wenruo [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=50dba73c-9b0b-636f-f44a-224cf355f6aa@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=ellisw@panasas.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).