From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-btrfs@vger.kernel.org
Subject: [GIT PULL] Btrfs updates for 2.6.31-rc
Date: Thu, 2 Jul 2009 15:10:35 -0400 [thread overview]
Message-ID: <20090702191035.GA3832@think> (raw)
Hello everyone,
Here are some btrfs updates. Most of them are small bug fixes, but the
large commit from Yan Zheng is step one in getting snapshot deletion
rolling. There is also has a nice CPU usage reduction for
streaming writes to a file.
Linus, please pull the master branch of btrfs-unstable:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master
Chris Mason (3) commits (+15/-9):
Btrfs: don't log the inode in file_write while growing the file (+4/-1)
Btrfs: fix the file clone ioctl for preallocated extents (+4/-2)
Btrfs: honor nodatacow/sum mount options for new files (+7/-6)
Josef Bacik (1) commits (+11/-1):
Btrfs: account for space we may use in fallocate
Yan Zheng (1) commits (+395/-181):
Btrfs: update backrefs while dropping snapshot
Total: (5) commits
fs/btrfs/ctree.h | 3
fs/btrfs/extent-tree.c | 564 +++++++++++++++++++++++++++++++++----------------
fs/btrfs/file.c | 5
fs/btrfs/inode.c | 25 +-
fs/btrfs/ioctl.c | 6
fs/btrfs/relocation.c | 5
fs/btrfs/transaction.c | 4
7 files changed, 421 insertions(+), 191 deletions(-)
next reply other threads:[~2009-07-02 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 19:10 Chris Mason [this message]
2009-07-02 19:46 ` [GIT PULL] Btrfs updates for 2.6.31-rc Chris Mason
-- strict thread matches above, loose matches on Subject: below --
2009-07-30 17:56 Chris Mason
2009-06-11 20:44 Chris Mason
2009-06-12 21:55 ` Linus Torvalds
2009-06-12 23:19 ` Theodore Tso
2009-06-13 0:18 ` 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=20090702191035.GA3832@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--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).