From: Josef Bacik <jbacik@fb.com>
To: Omar Sandoval <osandov@osandov.com>, <linux-btrfs@vger.kernel.org>
Cc: Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH 3/6] Btrfs: introduce the free space B-tree on-disk format
Date: Tue, 1 Sep 2015 15:28:29 -0400 [thread overview]
Message-ID: <55E5FC5D.2030701@fb.com> (raw)
In-Reply-To: <463b9e483192445e2fa0d258a2289f96b31018a3.1441131625.git.osandov@fb.com>
On 09/01/2015 03:02 PM, Omar Sandoval wrote:
> From: Omar Sandoval <osandov@fb.com>
>
> The on-disk format for the free space tree is straightforward. Each
> block group is represented in the free space tree by a free space info
> item that stores accounting information: whether the free space for this
> block group is stored as bitmaps or extents and how many extents of free
> space exist for this block group (regardless of which format is being
> used in the tree). Extents are (start, FREE_SPACE_EXTENT, length) keys
> with no corresponding item, and bitmaps instead have the
> FREE_SPACE_BITMAP type and have a bitmap item attached, which is just an
> array of bytes.
>
> Signed-off-by: Omar Sandoval <osandov@fb.com>
Reviewed-by: Josef Bacik <jbacik@fb.com>
Thanks,
Josef
next prev parent reply other threads:[~2015-09-01 19:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 19:01 [PATCH 0/6] free space B-tree Omar Sandoval
2015-09-01 19:01 ` [PATCH 1/6] Btrfs: add extent buffer bitmap operations Omar Sandoval
2015-09-01 19:25 ` Josef Bacik
2015-09-01 19:37 ` Omar Sandoval
2015-09-01 19:01 ` [PATCH 2/6] Btrfs: add helpers for read-only compat bits Omar Sandoval
2015-09-01 19:26 ` Josef Bacik
2015-09-01 19:01 ` [PATCH 3/6] Btrfs: introduce the free space B-tree on-disk format Omar Sandoval
2015-09-01 19:28 ` Josef Bacik [this message]
2015-09-01 19:05 ` [PATCH 5/6] Btrfs: wire up the free space tree to the extent tree Omar Sandoval
2015-09-01 19:48 ` Josef Bacik
2015-09-02 4:42 ` Omar Sandoval
2015-09-02 15:29 ` Josef Bacik
2015-09-01 19:05 ` [PATCH 6/6] Btrfs: add free space tree mount option Omar Sandoval
2015-09-01 19:49 ` Josef Bacik
2015-09-01 19:13 ` [PATCH 4/6] Btrfs: implement the free space B-tree Omar Sandoval
2015-09-01 19:44 ` Josef Bacik
2015-09-01 20:06 ` Omar Sandoval
2015-09-01 20:08 ` Josef Bacik
2015-09-01 19:17 ` [PATCH 0/6] " Omar Sandoval
2015-09-01 19:22 ` [PATCH 1/3] btrfs-progs: use calloc instead of malloc+memset for tree roots Omar Sandoval
2015-09-01 19:22 ` [PATCH 2/3] btrfs-progs: add basic awareness of the free space tree Omar Sandoval
2015-09-01 19:22 ` [PATCH 3/3] btrfs-progs: check the free space tree in btrfsck Omar Sandoval
2015-09-02 15:02 ` [PATCH 1/3] btrfs-progs: use calloc instead of malloc+memset for tree roots David Sterba
2015-09-03 19:44 ` [PATCH v2 0/9] free space B-tree Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 1/9] Btrfs: add extent buffer bitmap operations Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 2/9] Btrfs: add extent buffer bitmap sanity tests Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 3/9] Btrfs: add helpers for read-only compat bits Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 4/9] Btrfs: refactor caching_thread() Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 5/9] Btrfs: introduce the free space B-tree on-disk format Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 6/9] Btrfs: implement the free space B-tree Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 7/9] Btrfs: add free space tree sanity tests Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 8/9] Btrfs: wire up the free space tree to the extent tree Omar Sandoval
2015-09-04 5:56 ` Omar Sandoval
2015-09-03 19:44 ` [PATCH v2 9/9] Btrfs: add free space tree mount option Omar Sandoval
2015-09-09 12:00 ` David Sterba
2015-09-11 0:52 ` Omar Sandoval
2015-09-04 1:29 ` [PATCH v2 0/9] free space B-tree Zhao Lei
2015-09-04 5:43 ` Omar Sandoval
2015-09-11 1:21 ` Qu Wenruo
2015-09-11 3:48 ` Omar Sandoval
2015-09-11 3:58 ` Qu Wenruo
2015-09-11 4:15 ` Omar Sandoval
2015-09-22 14:41 ` David Sterba
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=55E5FC5D.2030701@fb.com \
--to=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=osandov@fb.com \
--cc=osandov@osandov.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 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.