From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Neal Gompa <ngompa13@gmail.com>
Cc: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Josef Bacik <josef@toxicpanda.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
David Sterba <dsterba@suse.com>,
Robbie Ko <robbieko@synology.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Subject: Re: About the state of Btrfs RAID 5/6
Date: Tue, 20 Apr 2021 23:09:43 +0000 [thread overview]
Message-ID: <BL0PR04MB65144CAE288491C3FC6B0757E7489@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: CAEg-Je-YxacuE4OweeAixCBV-RAGvWzNaKXcBoEyK_P2QcG6qQ@mail.gmail.com
On 2021/04/21 7:33, Neal Gompa wrote:
> On Thu, Sep 3, 2020 at 4:50 AM Damien Le Moal <Damien.LeMoal@wdc.com> wrote:
>>
>> On 2020/09/03 16:34, Johannes Thumshirn wrote:
>>> On 02/09/2020 19:37, Josef Bacik wrote:
>>>> I know Johannes is working on something magical,
>>>> but IDK what it is or how far out it is.
>>>
>>> That something is still slide-ware. I hopefully get back
>>> to really working on it soonish.
>>>
>>> So please don't expect patches within the next say 12 months.
>>
>> Come on... You can do better than that :)
>>
>> Joke aside, once we are past the zoned block device support (new version coming
>> this week), we will accelerate that work.
>>
>
> Now that we've got ZBD support landing with Linux 5.12 for Btrfs, any
> chance this might be looked at anytime soon?
Working on it. But this is not a small change so it will take a while for a
patch series to be posted.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2021-04-20 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:10 About the state of Btrfs RAID 5/6 Neal Gompa
2020-09-02 17:37 ` Josef Bacik
2020-09-02 18:18 ` Neal Gompa
2020-09-03 7:34 ` Johannes Thumshirn
2020-09-03 8:50 ` Damien Le Moal
2021-04-20 22:32 ` Neal Gompa
2021-04-20 23:09 ` Damien Le Moal [this message]
2020-09-03 15:02 ` Josef Bacik
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=BL0PR04MB65144CAE288491C3FC6B0757E7489@BL0PR04MB6514.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa13@gmail.com \
--cc=robbieko@synology.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;
as well as URLs for NNTP newsgroup(s).