From: Goffredo Baroncelli <kreijack@inwind.it>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: Hans van Kranenburg <hans@knorrie.org>,
linux-btrfs@vger.kernel.org, Michael <mclaud@roznica.com.ua>,
Hugo Mills <hugo@carfax.org.uk>,
Martin Svec <martin.svec@zoner.cz>,
Wang Yugui <wangyugui@e16-tech.com>,
Paul Jones <paul@pauljones.id.au>,
Adam Borowski <kilobyte@angband.pl>
Subject: Re: [RFC][PATCH V4] btrfs: preferred_metadata: preferred device for metadata
Date: Sat, 30 May 2020 13:51:53 +0200 [thread overview]
Message-ID: <035d901c-ba44-565e-3305-8999942c5d5d@inwind.it> (raw)
In-Reply-To: <20200530114431.GG10769@hungrycats.org>
On 5/30/20 1:44 PM, Zygo Blaxell wrote:
> On Fri, May 29, 2020 at 06:37:27PM +0200, Goffredo Baroncelli wrote:
>> On 5/28/20 11:59 PM, Hans van Kranenbu
[...]
>>> What are your thoughts about the chicken/egg situation of changing these
>>> properties only when the filesystem is mounted?
>>
>> The logic is related only to a chunk allocation. I.e. if you have a not
>> empty filesystem, after enabling the preferred_metadata "mode", in order
>> to get the benefit a full balance is required.
>
> Ideally this feature comes with a balance filter that selects block
> groups that don't match the current preferred allocation policy, so
> you can do a balance on those block groups and leave the rest alone.
> There are existing balance filters by devid and stripe count to work from,
> so it shouldn't be a lot of new kernel code.
>
Yes, this could be a further enhancement.
GB
--
gpg @keyserver.linux.it: Goffredo Baroncelli <kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
next prev parent reply other threads:[~2020-05-30 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 18:34 [RFC][PATCH V4] btrfs: preferred_metadata: preferred device for metadata Goffredo Baroncelli
2020-05-28 18:34 ` [PATCH 1/4] Add an ioctl to set/retrive the device properties Goffredo Baroncelli
2020-05-28 22:03 ` Hans van Kranenburg
2020-05-28 18:34 ` [PATCH 2/4] Add flags for dedicated metadata disks Goffredo Baroncelli
2020-05-28 18:34 ` [PATCH 3/4] Export dev_item.type in sysfs /sys/fs/btrfs/<uuid>/devinfo/<devid>/type Goffredo Baroncelli
2020-05-28 18:34 ` [PATCH 4/4] btrfs: add preferred_metadata mode Goffredo Baroncelli
2020-05-28 22:02 ` Hans van Kranenburg
2020-05-29 16:26 ` Goffredo Baroncelli
2020-05-28 21:59 ` [RFC][PATCH V4] btrfs: preferred_metadata: preferred device for metadata Hans van Kranenburg
2020-05-29 16:37 ` Goffredo Baroncelli
2020-05-30 11:44 ` Zygo Blaxell
2020-05-30 11:51 ` Goffredo Baroncelli [this message]
2021-01-08 1:05 ` Zygo Blaxell
2021-01-08 17:30 ` Goffredo Baroncelli
2021-01-08 17:43 ` BTRFS and *CACHE setup [was Re: [RFC][PATCH V4] btrfs: preferred_metadata: preferred device for metadata] Goffredo Baroncelli
2021-01-09 21:23 ` [RFC][PATCH V4] btrfs: preferred_metadata: preferred device for metadata Zygo Blaxell
2021-01-10 19:55 ` Goffredo Baroncelli
2021-01-16 0:25 ` Zygo Blaxell
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=035d901c-ba44-565e-3305-8999942c5d5d@inwind.it \
--to=kreijack@inwind.it \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=hans@knorrie.org \
--cc=hugo@carfax.org.uk \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.svec@zoner.cz \
--cc=mclaud@roznica.com.ua \
--cc=paul@pauljones.id.au \
--cc=wangyugui@e16-tech.com \
/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