public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] Btrfs updates for 2.6.30-rc (batch #2)
Date: Fri, 03 Apr 2009 15:32:58 -0400	[thread overview]
Message-ID: <1238787179.24082.7.camel@think.oraclecorp.com> (raw)

Hello everyone,

This is the second batch of btrfs updates for the merge window, which
includes an assortment of optimizations, fixes, cleanups and small
features.

>From a performance point of view, synchronous writes get a big boost by
making sure we unplug instead of letting kblockd do it for us, and Josef
got rid of two more mutexes from the allocator.

mount -o ssd is much faster in multi-process workloads, and it does a
better job of preventing free space fragmentation as well.

Linus, you'll find these changes in the master branch of:

git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git

Amit Gud (1):
      Btrfs: fix race in worker_loop

Chris Mason (5):
      Btrfs: keep processing bios for a given bdev if our proc is batching
      Btrfs: unplug in the async bio submission threads
      Btrfs: break up btrfs_search_slot into smaller pieces
      Btrfs: Optimize locking in btrfs_next_leaf()
      Btrfs: rework allocation clustering

Dan Carpenter (2):
      Btrfs: remove dead code
      Btrfs: remove dead code

Eric Paris (1):
      Btrfs: introduce btrfs_show_options

Heiko Carstens (1):
      Btrfs: fix __ucmpdi2 compile bug on 32 bit builds

Jim Owens (1):
      Btrfs: remove unused ftrace include

Josef Bacik (4):
      Btrfs: free space cache cleanups
      Btrfs: clean up find_free_extent
      Btrfs: kill the block group alloc mutex
      Btrfs: kill the pinned_mutex

Sage Weil (2):
      Btrfs: notreelog mount option
      Btrfs: add flushoncommit mount option

Shen Feng (1):
      Btrfs: free inode struct when btrfs_new_inode fails

Stoyan Gaydarov (1):
      Btrfs: BUG to BUG_ON changes

Wu Fengguang (1):
      Btrfs: fix typos in comments

 fs/btrfs/async-thread.c     |    7
 fs/btrfs/ctree.c            |  312 ++++++++++++++++---------
 fs/btrfs/ctree.h            |   84 ++++--
 fs/btrfs/delayed-ref.c      |    1
 fs/btrfs/disk-io.c          |    8
 fs/btrfs/extent-tree.c      |  398 ++++++++++++++++-----------------
 fs/btrfs/extent_io.c        |   16 -
 fs/btrfs/extent_map.c       |    1
 fs/btrfs/free-space-cache.c |  530 +++++++++++++++++++++++++++++++-------------
 fs/btrfs/free-space-cache.h |   44 +++
 fs/btrfs/inode.c            |    5
 fs/btrfs/locking.c          |    4
 fs/btrfs/super.c            |   54 ++++
 fs/btrfs/transaction.c      |    7
 fs/btrfs/tree-log.c         |   12
 fs/btrfs/volumes.c          |   41 +++
 fs/btrfs/volumes.h          |    2
 17 files changed, 982 insertions(+), 544 deletions(-)



             reply	other threads:[~2009-04-03 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 19:32 Chris Mason [this message]
2009-04-08 23:48 ` [2.6.30-rc1] gpf in btrfs during shutdown Ed Tomlinson
2009-04-09  0:14   ` Chris Mason
2009-04-09  1:55     ` Ed Tomlinson
2009-04-09  2:36       ` Chris Mason

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=1238787179.24082.7.camel@think.oraclecorp.com \
    --to=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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