From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <dsterba@suse.cz>
Cc: "'Chris Mason'" <clm@fb.com>, "'btrfs'" <linux-btrfs@vger.kernel.org>
Subject: RE: [GIT PULL] Fujitsu for 4.5
Date: Fri, 15 Jan 2016 17:46:42 +0800 [thread overview]
Message-ID: <01e901d14f79$a4adb660$ee092320$@cn.fujitsu.com> (raw)
In-Reply-To: <20160114141710.GW4227@twin.jikos.cz>
Hi, David Sterba
> From: David Sterba [mailto:dsterba@suse.cz]
> Sent: Thursday, January 14, 2016 10:17 PM
> To: Zhao Lei <zhaolei@cn.fujitsu.com>
> Cc: 'Chris Mason' <clm@fb.com>; 'btrfs' <linux-btrfs@vger.kernel.org>
> Subject: Re: [GIT PULL] Fujitsu for 4.5
>
> On Wed, Jan 13, 2016 at 05:28:12PM +0800, Zhao Lei wrote:
> > 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.
> >
> > Would you please consider merging the following fixes to integration-4.5
> branch?
>
> > Zhao Lei (26):
> ...
> > 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: reada: limit max works count
> > btrfs: reada: simplify dev->reada_in_flight processing
>
> I have reviewed the readahead patches and ack them for 4.5.
Great thanks for reviewing these patchs.
And following 3 patchs in this branch are also for readahead, but sorry that
I forgot adding "reada" prefix in subject.
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
Would you please consider helping me to review them?
Thanks
Zhaolei
next prev parent reply other threads:[~2016-01-15 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 9:28 [GIT PULL] Fujitsu for 4.5 Zhao Lei
2016-01-14 14:17 ` David Sterba
2016-01-15 9:46 ` Zhao Lei [this message]
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='01e901d14f79$a4adb660$ee092320$@cn.fujitsu.com' \
--to=zhaolei@cn.fujitsu.com \
--cc=clm@fb.com \
--cc=dsterba@suse.cz \
--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).