From: David Sterba <dsterba@suse.cz>
To: kreijack@inwind.it
Cc: Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH v2 00/10] btrfs-progs: mkfs fixes and prep work for extent tree v2
Date: Mon, 11 Oct 2021 20:47:16 +0200 [thread overview]
Message-ID: <20211011184716.GT9286@suse.cz> (raw)
In-Reply-To: <03ae7a36-dbc9-bfad-6ec7-45e929f862a7@libero.it>
On Mon, Oct 11, 2021 at 08:35:53PM +0200, Goffredo Baroncelli wrote:
> On 8/25/21 3:58 PM, David Sterba wrote:
> > On Mon, Aug 23, 2021 at 04:14:45PM -0400, Josef Bacik wrote:
> [...]
> > Even with the "if (EXTENT_TREE_V2)" in place it becomes the
> > implementation and given that I haven't read the whole design doc for
> > that I'm worried that once I find time for that and would suggest some
> > changes the reply would be "no I did it this way, it's implemented,
> > would require too many changes".
>
> Just for curiosity, is there anywhere a design doc for extent tree v2 ?
https://github.com/btrfs/btrfs-todo/issues/25 but it's more like an
ongoing discussion than a polished design doc, that's about to be a
result of that some day.
next prev parent reply other threads:[~2021-10-11 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 20:14 [PATCH v2 00/10] btrfs-progs: mkfs fixes and prep work for extent tree v2 Josef Bacik
2021-08-23 20:14 ` [PATCH v2 01/10] btrfs-progs: mkfs: use an associative array for init blocks Josef Bacik
2021-08-23 20:14 ` [PATCH v2 02/10] btrfs-progs: mkfs: get rid of MKFS_SUPER_BLOCK Josef Bacik
2021-08-23 20:14 ` [PATCH v2 03/10] btrfs-progs: mkfs: use blocks_nr to determine the super used bytes Josef Bacik
2021-08-23 20:14 ` [PATCH v2 04/10] btrfs-progs: mkfs: set nritems based on root items written Josef Bacik
2021-08-23 20:14 ` [PATCH v2 05/10] btrfs-progs: mkfs: add helper for writing empty tree nodes Josef Bacik
2021-08-23 20:14 ` [PATCH v2 06/10] btrfs-progs: make sure track_dirty and ref_cows is set properly Josef Bacik
2021-08-23 20:14 ` [PATCH v2 07/10] btrfs-progs: mkfs: add the block group item in make_btrfs() Josef Bacik
2021-08-23 20:14 ` [PATCH v2 08/10] btrfs-progs: add add_block_group_free_space helper Josef Bacik
2021-08-23 20:14 ` [PATCH v2 09/10] btrfs-progs: mkfs: generate free space tree at make_btrfs() time Josef Bacik
2021-10-11 1:24 ` Qu Wenruo
2021-08-23 20:14 ` [PATCH v2 10/10] btrfs-progs: add the incompat flag for extent tree v2 Josef Bacik
2021-08-25 13:58 ` [PATCH v2 00/10] btrfs-progs: mkfs fixes and prep work " David Sterba
2021-09-03 13:53 ` David Sterba
2021-10-11 18:35 ` Goffredo Baroncelli
2021-10-11 18:47 ` David Sterba [this message]
2021-10-11 19:39 ` Goffredo Baroncelli
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=20211011184716.GT9286@suse.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.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 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).