From: Goffredo Baroncelli <kreijack@libero.it>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
linux-btrfs@vger.kernel.org
Subject: Re: [RFC][PATCH V5] btrfs: preferred_metadata: preferred device for metadata
Date: Sun, 15 Jan 2023 18:05:01 +0100 [thread overview]
Message-ID: <6433005a-21c8-fc9b-6fbd-ae9727751ca5@libero.it> (raw)
In-Reply-To: <83f2e6f7-2513-6da1-6078-56ca6420d8e5@libero.it>
On 15/01/2023 18.00, Goffredo Baroncelli wrote:
> On 25/01/2021 16.21, Josef Bacik wrote:
> [...]
>> Ok this discussion is going in a few different directions, and there's a lot of moving parts here. I don't want Goffredo to wander off and do V6 only to have us go off into the weeds on random particulars of how we think this thing is supposed to work. To that end, I've opened a design issue in github
>>
>> https://github.com/btrfs/btrfs-todo/issues/19
>>
>> and filled out what I think are all the questions and points we've all brought up throughout these discussions. Everybody please weigh in on the task, laying out what they think is the best way forward for some/all of these questions. Once we have an agreed upon design then Goffredo can go and do V6, and then we only have to argue about the code and not the design. Thanks,
>>
>
> Hi Josef,
> do you think that there will be interest in resurrecting this patches ?
>
> I saw some form of interesting by MarkRose (see github https://github.com/btrfs/btrfs-todo/issues/19#issuecomment-1368377759)
>
>> Josef
Ok, the latest updates was a V12 version:
[PATCH 0/5][V12] btrfs: allocation_hint
https://lore.kernel.org/linux-btrfs/cover.1646589622.git.kreijack@inwind.it/
>
--
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:[~2023-01-15 17:05 UTC|newest]
Thread overview: 27+ 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-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
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 [this message]
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=6433005a-21c8-fc9b-6fbd-ae9727751ca5@libero.it \
--to=kreijack@libero.it \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=josef@toxicpanda.com \
--cc=kreijack@inwind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.