From: Chris Mason <chris.mason@oracle.com>
To: "Linus" <torvalds@linux-foundation.org>,
"linux-btrfs" <linux-btrfs@vger.kernel.org>,
"Linux-kernel" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Btrfs updates
Date: Sat, 04 Jun 2011 10:37:18 -0400 [thread overview]
Message-ID: <1307197108-sup-8188@shiny> (raw)
Hi everyone,
The for-linus branch of the btrfs unstable repo:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git for-linus
Has our collection of fixes. It's a little bigger than usual for rc2
because it includes Josef's queue of Btrfs changes. It seemed best to
split them so we could concentrate on looking for any issues in the new
btrfs rc1 code from Fujitsu. His tree is bug fixes and journal lock
reduction.
Some people have reported the initial caching of the free inode number
map (which happens only once when it is first enabled) is sucking down
too much CPU and IO time on their systems. We don't have that one fixed
yet, but this pull does clean up a few other problems in the new inode
number allocatgor. It also turns it off by default (mount -o
inode_cache to enable).
I was on the fence for turning this on by default, but we've already
kicked out three bugs so it seems best to keep it optional until 3.1.
Josef Bacik (15) commits (+478/-386):
Btrfs: don't try to allocate from a block group that doesn't have enough space (+8/-0)
Btrfs: take away the num_items argument from btrfs_join_transaction (+42/-48)
Btrfs: make sure to use the delalloc reserve when filling delalloc (+2/-0)
Btrfs: don't save the inode cache if we are deleting this root (+5/-0)
Btrfs: don't look at the extent buffer level 3 times in a row (+0/-3)
Btrfs: map the node block when looking for readahead targets (+21/-2)
Btrfs: set range_start to the right start in count_range_bits (+1/-1)
Btrfs: if we've already started a trans handle, use that one (+19/-0)
Btrfs: check for duplicate entries in the free space cache (+24/-3)
Btrfs: try not to sleep as much when doing slow caching (+11/-8)
Btrfs: fix how we do space reservation for truncate (+123/-37)
Btrfs: leave spinning on lookup and map the leaf (+12/-0)
Btrfs: kill BTRFS_I(inode)->block_group (+13/-110)
Btrfs: don't always do readahead (+20/-5)
Btrfs: kill trans_mutex (+177/-169)
Chris Mason (3) commits (+54/-9):
Btrfs: make sure we don't overflow the free space cache crc page (+19/-8)
Btrfs: fix uninit variable in the delayed inode code (+1/-0)
Btrfs: add mount -o inode_cache (+34/-1)
David Sterba (3) commits (+26/-21):
btrfs: use btrfs_ino to access inode number (+5/-4)
btrfs: fix uninitialized variable warning (+1/-1)
btrfs: add helper for fs_info->closing (+20/-16)
Arne Jansen (3) commits (+70/-53):
btrfs: scrub: don't reuse bios and pages (+65/-49)
btrfs: scrub: add explicit plugging (+4/-3)
btrfs: false BUG_ON when degraded (+1/-1)
liubo (1) commits (+6/-0):
Btrfs: don't save the inode cache in non-FS roots
Total: (25) commits
fs/btrfs/btrfs_inode.h | 3 -
fs/btrfs/ctree.c | 28 +++-
fs/btrfs/ctree.h | 22 +++-
fs/btrfs/delayed-inode.c | 8 +-
fs/btrfs/disk-io.c | 36 +++---
fs/btrfs/extent-tree.c | 103 ++++++++++-----
fs/btrfs/extent_io.c | 2 +-
fs/btrfs/file.c | 10 +-
fs/btrfs/free-space-cache.c | 70 ++++++++---
fs/btrfs/inode-map.c | 34 +++++-
fs/btrfs/inode.c | 261 +++++++++++++++++++------------------
fs/btrfs/ioctl.c | 26 ++---
fs/btrfs/relocation.c | 34 +++--
fs/btrfs/scrub.c | 123 ++++++++++--------
fs/btrfs/super.c | 8 +-
fs/btrfs/transaction.c | 302 +++++++++++++++++++++++--------------------
fs/btrfs/transaction.h | 29 +---
fs/btrfs/volumes.c | 2 +-
fs/btrfs/xattr.c | 2 -
19 files changed, 635 insertions(+), 468 deletions(-)
next reply other threads:[~2011-06-04 14:37 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-04 14:37 Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-18 14:30 [GIT PULL] Btrfs updates Chris Mason
2013-03-29 17:47 Chris Mason
2013-03-09 0:38 Chris Mason
2013-02-16 1:55 Chris Mason
2012-12-17 21:44 Chris Mason
2012-12-19 18:09 ` Roy Sigurd Karlsbakk
2012-12-19 19:07 ` Hugo Mills
2012-12-17 21:28 Chris Mason
2012-08-29 16:01 Chris Mason
2012-07-05 19:55 Chris Mason
2012-06-21 15:47 Chris Mason
2012-06-15 18:09 Chris Mason
2012-06-15 23:57 ` Linus Torvalds
2012-06-16 0:21 ` Chris Mason
2012-06-01 13:18 Chris Mason
2012-04-13 13:38 Chris Mason
2012-04-16 1:19 ` Tsutomu Itoh
2012-03-10 2:01 Chris Mason
2012-02-24 16:41 Chris Mason
2011-12-01 15:39 Chris Mason
2011-12-05 8:10 ` Miao Xie
2011-12-05 13:14 ` Chris Mason
2011-12-05 14:08 ` David Sterba
2011-12-06 3:25 ` Miao Xie
2011-08-18 18:04 Chris Mason
2011-08-18 21:51 ` Sage Weil
2011-08-20 14:01 ` Chris Mason
2011-07-27 22:46 Chris Mason
2011-06-27 18:15 Chris Mason
2011-06-20 1:12 Chris Mason
2011-06-12 11:57 Chris Mason
2011-06-12 18:08 ` Linus Torvalds
2011-06-13 1:02 ` Andi Kleen
2011-06-13 1:52 ` Chris Mason
2011-06-13 2:05 ` Li Zefan
2011-05-27 19:55 Chris Mason
2011-05-27 21:44 ` Chester
2011-05-15 14:47 Chris Mason
2011-05-15 15:41 ` kehon
2011-04-26 14:24 Chris Mason
2011-04-18 14:26 Chris Mason
2011-02-15 3:49 Chris Mason
2011-02-07 20:12 Chris Mason
2011-02-08 20:05 ` Helmut Hullen
2011-01-17 21:13 Chris Mason
2011-01-18 10:14 ` Felix Blanke
2011-01-18 15:22 ` C Anthony Risinger
2011-01-18 17:56 ` Mitch Harder
2011-01-18 18:51 ` C Anthony Risinger
2011-01-19 9:15 ` Spelic
2011-01-22 23:41 ` Clemens Eisserer
2011-01-22 23:53 ` cwillu
2011-01-18 18:55 ` Goffredo Baroncelli
2011-03-09 22:01 ` Diego Calleja
2010-12-14 1:54 Chris Mason
2010-05-27 15:15 Chris Mason
2010-05-27 17:18 ` Linus Torvalds
2010-05-27 17:32 ` Chris Mason
2010-05-27 17:47 ` Linus Torvalds
2010-06-02 2:59 ` Miao Xie
2010-09-12 12:38 ` Felipe Contreras
2010-04-05 19:36 Chris Mason
2010-04-06 15:40 ` Chris Mason
2010-03-15 19:18 Chris Mason
2010-03-16 21:01 ` Chris Mason
2010-03-18 16:59 ` Chris Mason
2009-10-15 0:06 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=1307197108-sup-8188@shiny \
--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).