From: Chris Mason <chris.mason@oracle.com>
To: Josef Bacik <josef@redhat.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC] new free space caching stuff
Date: Fri, 22 May 2009 10:11:34 -0400 [thread overview]
Message-ID: <20090522141133.GA8762@think> (raw)
In-Reply-To: <20090521184351.GC11101@dhcp231-156.rdu.redhat.com>
On Thu, May 21, 2009 at 02:43:52PM -0400, Josef Bacik wrote:
> Hello,
>
> Okay I'm looking at redoing all of this stuff again, and I'd like to make this
> the last time, so I'm going to outline what we currently have, what the problems
> are with it, and what I want to do. I would appreciate any/all input so I can
> try and get this right the first time.
>
Josef and I hashed this out someone on IRC. I think the bitmaps alone
aren't going to scale all that well for huge filesystems, so he is
looking into a hybrid bitmap/extent approach based on the size of the
free space.
-chris
next prev parent reply other threads:[~2009-05-22 14:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 18:43 [RFC] new free space caching stuff Josef Bacik
2009-05-22 14:11 ` Chris Mason [this message]
2009-05-26 16:12 ` Linda Knippers
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=20090522141133.GA8762@think \
--to=chris.mason@oracle.com \
--cc=josef@redhat.com \
--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.