From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: Josef Bacik <josef@toxicpanda.com>,
Goffredo Baroncelli <kreijack@libero.it>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Cc: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Subject: Re: [RFC][PATCH V5] btrfs: preferred_metadata: preferred device for metadata
Date: Wed, 20 Jan 2021 16:15:27 +0000 [thread overview]
Message-ID: <SN4PR0401MB35989479F9B02A1E2795728F9BA20@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 30cd0359-e649-dcc7-e373-4dd778fbf70b@toxicpanda.com
On 20/01/2021 17:09, Josef Bacik wrote:
> I'm not against adding new actual keys and items
> to the tree itself, but is there a way we could use our existing property
> infrastructure that we use for compression, and simply store the xattrs in the
> tree root? It looks like we're just toggling a policy decision, and we don't
> actually need the other properties in the item you've created, so why not just a
> btrfs.preferred_metadata property with the value stored in it, dropped into the
> tree_root so it can be read on mount?
+1 from my side as well.
I have the need for this in a planned/future series and I'd be more than happy if
someone else would've already implemented it so I can jump on the train there.
next prev parent reply other threads:[~2021-01-20 16:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 18:54 [RFC][PATCH V5] btrfs: preferred_metadata: preferred device for metadata Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 1/5] Add an ioctl to set the device properties Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 2/5] Add flags for dedicated metadata disks Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 3/5] Export dev_item.type in sysfs /sys/fs/btrfs/<uuid>/devinfo/<devid>/type Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 4/5] btrfs: add preferred_metadata option Goffredo Baroncelli
2021-01-17 18:54 ` [PATCH 5/5] btrfs: add preferred_metadata mode mount option Goffredo Baroncelli
2021-01-18 3:05 ` kernel test robot
2021-01-19 23:12 ` [RFC][PATCH V5] btrfs: preferred_metadata: preferred device for metadata Zygo Blaxell
2021-01-21 8:31 ` Martin Svec
2021-01-20 16:02 ` Josef Bacik
2021-01-20 16:15 ` Johannes Thumshirn [this message]
2021-01-20 16:17 ` Josef Bacik
2021-01-20 16:20 ` Zygo Blaxell
2021-01-21 18:16 ` Goffredo Baroncelli
2021-01-21 18:54 ` Zygo Blaxell
2021-01-22 18:31 ` Goffredo Baroncelli
2021-01-22 22:42 ` Zygo Blaxell
2021-01-23 14:55 ` Graham Cobb
2021-01-23 17:21 ` Zygo Blaxell
2021-01-23 17:44 ` Graham Cobb
2021-01-24 4:00 ` Zygo Blaxell
2021-01-24 20:05 ` Goffredo Baroncelli
2021-01-25 15:21 ` Josef Bacik
2023-01-15 17:00 ` Goffredo Baroncelli
2023-01-15 17:05 ` Goffredo Baroncelli
2023-01-16 8:20 ` Paul Jones
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=SN4PR0401MB35989479F9B02A1E2795728F9BA20@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=josef@toxicpanda.com \
--cc=kreijack@libero.it \
--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).