From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: "'Chris Mason'" <clm@fb.com>
Cc: "'btrfs'" <linux-btrfs@vger.kernel.org>, <zhaolei@cn.fujitsu.com>
Subject: [GIT PULL] Fujitsu for 4.5
Date: Wed, 13 Jan 2016 17:28:12 +0800 [thread overview]
Message-ID: <01ad01d14de4$b9489900$2bd9cb00$@cn.fujitsu.com> (raw)
Hi Chris,
This is collection of some bug fix, enhance and cleanup from fujitsu
against btrfs for v4.5, mainly for reada, plus some small fix and cleanup
for scrub and raid56.
All patchs are in btrfs-maillist, rebased on top of integration-4.5.
TEST STATUS:
Tested by xfstests, btrfs and generic group with default mount option,
diffed result with 4.4-rc8 and confirmed no regression:
Diff From:
dir=/var/ltf/testqueue/v4.4-rc8/xfstests/
head=v4.4-rc8
Diff To:
dir=/var/ltf/testqueue/8e16378041f7f3531c256fd3e17a36a4fca92d29
head=v4.4-rc6_00037_8e1637
Test:
node=ALL
Decrease items:
none
Xfstests for other 9 mount options is in running, I'll check results after finished.
Would you please consider merging the following fixes to integration-4.5 branch?
REPO is:
https://github.com/zhaoleidd/btrfs.git integration-4.5
--
Zhao Lei (26):
btrfs: Small cleanup for get index_srcdev loop
btrfs: Use direct way to determine raid56 write/recover mode
btrfs: Fix in-segment calculation for reada
btrfs: reduce additional fs_info->reada_lock in reada_find_zone
btrfs: Add missed segment checking in reada_find_zone
btrfs: reada: Avoid many times of empty loop
btrfs: reada: Move is_need_to_readahead contition earlier
btrfs: reada: add all reachable mirrors into reada device list
btrfs: reada: bypass adding extent when all zone failed
btrfs: reada: Remove level argument in severial functions
btrfs: reada: move reada_extent_put to place after __readahead_hook()
btrfs: reada: Pass reada_extent into __readahead_hook directly
btrfs: reada: Use fs_info instead of root in __readahead_hook's
argument
btrfs: reada: Jump into cleanup in direct way for __readahead_hook()
btrfs: reada: Fix a debug code typo
btrfs: Continue write in case of can_not_nocow
btrfs: delete no_used argument in btrfs_copy_from_user
btrfs: merge functions for wait snapshot creation
btrfs: reada: limit max works count
btrfs: reada: simplify dev->reada_in_flight processing
btrfs: Fix no_space in write and rm loop
btrfs: Fix calculation of rbio->dbitmap's size calculation
btrfs: Use unified stripe_page's index calculation
btrfs: use rbio->nr_pages to reduce calculation
btrfs: Remove unnecessary ClearPageUptodate for raid56
btrfs: raid56: Use raid_write_end_io for scrub
fs/btrfs/ctree.h | 5 +-
fs/btrfs/disk-io.c | 22 ++---
fs/btrfs/extent-tree.c | 24 +++++-
fs/btrfs/file.c | 43 +++++-----
fs/btrfs/inode.c | 22 +----
fs/btrfs/raid56.c | 100 ++++++++--------------
fs/btrfs/reada.c | 224 ++++++++++++++++++++++++-------------------------
fs/btrfs/scrub.c | 2 +-
fs/btrfs/volumes.c | 45 +++++-----
9 files changed, 225 insertions(+), 262 deletions(-)
Thanks
Zhaolei
next reply other threads:[~2016-01-13 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:28 Zhao Lei [this message]
2016-01-14 14:17 ` [GIT PULL] Fujitsu for 4.5 David Sterba
2016-01-15 9:46 ` Zhao Lei
2016-01-15 16:49 ` David Sterba
2016-01-18 11:02 ` Zhao Lei
2016-01-15 16:12 ` Chris Mason
2016-02-10 10:13 ` David Sterba
2016-02-15 4:07 ` Zhao Lei
2016-02-16 10:05 ` David Sterba
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='01ad01d14de4$b9489900$2bd9cb00$@cn.fujitsu.com' \
--to=zhaolei@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.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).