public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hp.com>
To: Chris Mason <chris.mason@oracle.com>,
	Josef Bacik <josef@redhat.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [RFC] new free space caching stuff
Date: Tue, 26 May 2009 12:12:21 -0400	[thread overview]
Message-ID: <4A1C14E5.2050601@hp.com> (raw)
In-Reply-To: <20090522141133.GA8762@think>

Chris Mason wrote:
> 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.

I don't know if this is of any interest but I thought I'd provide a
pointer to the AdvFS design spec for space allocation.
http://advfs.svn.sourceforge.net/viewvc/advfs/advfs_design_docs_v1/porting_designs/storage_allocation.pdf?revision=1

The Tru64 version of AdvFS used bitmaps but this was changed during the
port to HP-UX to
use a combination of b-trees.  Both the original and new designs are
discussed in
section 2 of the spec and there's a description of other design options
considered but then rejected.

The docs in the original tarball I posted were not very user friendly so
I checked them into an svc tree to make them a little easier to browse.
If it will be useful, I can do the same with the source code.

-- ljk

> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      reply	other threads:[~2009-05-26 16:12 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
2009-05-26 16:12   ` Linda Knippers [this message]

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=4A1C14E5.2050601@hp.com \
    --to=linda.knippers@hp.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox