From: Chris Mason <chris.mason@oracle.com>
To: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [GIT PULL] Btrfs updates for 2.6.29-rc
Date: Fri, 13 Feb 2009 15:25:55 -0500 [thread overview]
Message-ID: <1234556755.4985.7.camel@think.oraclecorp.com> (raw)
Hello everyone,
The master branch
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git
Has the following fixes and updates for 2.6.29-rc. There is also a
branch named experimental that is very very experimental.
I think I pushed things out correctly so that master and experimental
didn't mix, but we've long established my ability to mess that part up.
These are cleanups and fixes that came out of testing and review. The
lockdep fix is actually the biggest in terms of code, but that is under
CONFIG_DEBUG_LOCK_ALLOC.
SSD mode is changed to work better on ssds that do random writes poorly,
and btrfs_sync_fs is changed to skip the cleaning of old snapshots.
That still happens in the background, and it was making sync look slower
than it really was.
mount -o remount finally looks at the new options sent, so you can send
important things like mount -o compress,ssd for remounting now.
-chris
Chris Mason (4):
Btrfs: process mount options on mount -o remount,
Btrfs: use larger metadata clusters in ssd mode
Btrfs: don't clean old snapshots on sync(1)
Btrfs: make a lockdep class for the extent buffer locks
Jeff Mahoney (2):
Btrfs: balance_level checks !child after access
Btrfs: remove btrfs_init_path
Josef Bacik (1):
Btrfs: make sure all pending extent operations are complete
Julia Lawall (1):
Btrfs: fs/btrfs/volumes.c: remove useless kzalloc
Qinghuang Feng (1):
Btrfs: remove unused code in split_state()
Yan Zheng (2):
Btrfs: Avoid using __GFP_HIGHMEM with slab allocator
Btrfs: hold trans_mutex when using btrfs_record_root_in_trans
b/fs/btrfs/ctree.c | 45 +++++++++++++++++++-------
b/fs/btrfs/ctree.h | 10 +----
b/fs/btrfs/disk-io.c | 46 ++++++++++++++++++++++++++
b/fs/btrfs/disk-io.h | 10 +++++
b/fs/btrfs/extent-tree.c | 2 +
b/fs/btrfs/extent_io.c | 2 -
b/fs/btrfs/inode-map.c | 1
b/fs/btrfs/inode.c | 2 -
b/fs/btrfs/locking.c | 11 ------
b/fs/btrfs/super.c | 1
b/fs/btrfs/transaction.c | 2 +
b/fs/btrfs/tree-log.c | 2 +
b/fs/btrfs/volumes.c | 2 +
fs/btrfs/ctree.c | 13 +------
fs/btrfs/ctree.h | 1
fs/btrfs/extent-tree.c | 81 ++++++++++++++++++++++++++++-------------------
fs/btrfs/inode.c | 2 -
fs/btrfs/super.c | 4 ++
fs/btrfs/volumes.c | 4 --
19 files changed, 157 insertions(+), 84 deletions(-)
next reply other threads:[~2009-02-13 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 20:25 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-26 15:11 [GIT PULL] Btrfs updates for 2.6.29-rc Chris Mason
2009-02-26 15:09 Chris Mason
2009-02-06 16:22 Chris Mason
2009-02-06 16:53 ` Linus Torvalds
2009-02-06 21:51 ` Chris Mason
2009-02-06 21:59 ` Linus Torvalds
2009-02-07 0:10 ` Chris Mason
2009-02-07 16:37 ` Linus Torvalds
2009-02-07 23:50 ` Chris Mason
2009-02-08 10:16 ` Kay Sievers
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=1234556755.4985.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;
as well as URLs for NNTP newsgroup(s).