linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH 2/2] Btrfs: introduce free space cluster for each node
Date: Wed, 02 Nov 2011 10:16:31 +0800	[thread overview]
Message-ID: <4EB0A7FF.8060602@cn.fujitsu.com> (raw)
In-Reply-To: <20111101160440.GA13340@shiny>

On tue, 1 Nov 2011 12:04:40 -0400, Chris Mason wrote:
> On Tue, Nov 01, 2011 at 03:39:11PM +0800, Miao Xie wrote:
>> Any Comment?
> 
> This is definitely interesting, in terms of trying to avoid btree
> fragmentation and improve the performance of the allocator.
> 
> But I'm worried about what happens to performance as the FS fills up?
> What kind of benchmarks have you done on larger filesystems that are
> almost full?

Sorry, I have not done test in this condition.
I think you are right, on the filesystems that are almost full, the performance
will go down. My next work may fix this problem, that is:
I. the buddy system of the free space (just like the buddy system of the memory management)
II. pre-node cluster degradation on almost full filesystems (If the free space is not enough,
    use the global cluster)
    Or maybe we can use the cluster of other nodes to allocate free space instead of pre-node
    cluster degradation

Thanks
Miao Xie


> 
> -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:[~2011-11-02  2:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08  8:18 [RFC PATCH 2/2] Btrfs: introduce free space cluster for each node Miao Xie
2011-11-01  7:39 ` Miao Xie
2011-11-01 16:04   ` Chris Mason
2011-11-02  2:16     ` Miao Xie [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=4EB0A7FF.8060602@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=chris.mason@oracle.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;
as well as URLs for NNTP newsgroup(s).