linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
	Miao Xie <miaox@cn.fujitsu.com>, Arne Jansen <sensille@gmx.net>
Subject: Re: Integration branch pushed out to btrfs-unstable
Date: Tue, 24 May 2011 17:50:20 +0800	[thread overview]
Message-ID: <4DDB7F5C.8050004@cn.fujitsu.com> (raw)
In-Reply-To: <1306179381-sup-443@shiny>

Chris Mason wrote:
> Hi everyone,
> 
> I've pushed out my current kernel git tree to a new branch called
> integration-test.  This is meant for integration testing only and should
> not be run by anyone who doesn't love crashes.
> 
> I've pulled together a lot of important work from a lot of different
> people.  It includes:
> 
> The new inode number allocator
> Delayed inode and directory item updates
> Scrub, chunk allocator fixes
> Races in device addition and removal
> Josef's performance fixes
> A large series of cleanups and fixes
> 
> Most of the integration work was just pushing the cleanups into the new
> code bits.  I still want to integrate Hugo Mills' balance progress
> ioctls (really nice).  But it was a lot of work to get this all working
> together and I wanted to let everyone retest the result.
> 
> Miao, I didn't include your patch to delay inode item insertion because
> I was worried about interactions with the caching thread of the new
> inode number allocator.  I did have to make a small change to make sure
> the inode-map cache didn't go through the delayed item routines.
> 
> Li, one thing I haven't done yet is a lot of benchmarking on the
> performance hit from waiting for the cache to fill on large existing
> filesystems.  Was there any particular reason you didn't setup the
> caching to pre-cache the from root->highest_objectid to
> BTRFS_LAST_FREE_OBJECTID?
> 

I'll cook up a patch for this kind of pre-cache.

  parent reply	other threads:[~2011-05-24  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 19:54 Integration branch pushed out to btrfs-unstable Chris Mason
2011-05-24  9:01 ` Arne Jansen
2011-05-24  9:50 ` Li Zefan [this message]
2011-05-25 12:35 ` Arne Jansen
2011-05-25 18:44   ` Sergei Trofimovich
2011-05-25 20:41     ` Sergei Trofimovich

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=4DDB7F5C.8050004@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=miaox@cn.fujitsu.com \
    --cc=sensille@gmx.net \
    /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).