linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raghavendra D Prabhu <raghu.prabhu13@gmail.com>
To: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	zheng.yan@oracle.com, linux-mm@kvack.org,
	linux-btrfs@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Change the check for PageReadahead into an else-if
Date: Thu, 25 Oct 2012 02:14:07 +0530	[thread overview]
Message-ID: <20121024204407.GA3218@Archie> (raw)
In-Reply-To: <CAHGf_=qxMv20bNg2FZLCO2Ra0S+zTicxQEXu=nOTc-f3kiWj-Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]

Hi,


* On Tue, Oct 16, 2012 at 10:02:44PM -0400, KOSAKI Motohiro <kosaki.motohiro@gmail.com> wrote:
>On Tue, Oct 16, 2012 at 10:00 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>> On Wed, Oct 17, 2012 at 12:28:05AM +0530, raghu.prabhu13@gmail.com wrote:
>>> From: Raghavendra D Prabhu <rprabhu@wnohang.net>
>>>
>>> >From 51daa88ebd8e0d437289f589af29d4b39379ea76, page_sync_readahead coalesces
>>> async readahead into its readahead window, so another checking for that again is
>>> not required.
>>>
>>> Signed-off-by: Raghavendra D Prabhu <rprabhu@wnohang.net>
>>> ---
>>>  fs/btrfs/relocation.c | 10 ++++------
>>>  mm/filemap.c          |  3 +--
>>>  2 files changed, 5 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/fs/btrfs/relocation.c b/fs/btrfs/relocation.c
>>> index 4da0865..6362003 100644
>>
>>> --- a/fs/btrfs/relocation.c
>>> +++ b/fs/btrfs/relocation.c
>>> @@ -2996,12 +2996,10 @@ static int relocate_file_extent_cluster(struct inode *inode,
>>>                               ret = -ENOMEM;
>>>                               goto out;
>>>                       }
>>> -             }
>>> -
>>> -             if (PageReadahead(page)) {
>>> -                     page_cache_async_readahead(inode->i_mapping,
>>> -                                                ra, NULL, page, index,
>>> -                                                last_index + 1 - index);
>>> +             } else if (PageReadahead(page)) {
>>> +                             page_cache_async_readahead(inode->i_mapping,
>>> +                                                     ra, NULL, page, index,
>>> +                                                     last_index + 1 - index);
>>
>> That extra indent is not necessary.
>>
>> Otherwise looks good to me. Thanks!
>>
>> Reviewed-by: Fengguang Wu <fengguang.wu@intel.com>
>
>Hi Raghavendra,
>
>Indentation breakage is now welcome. Please respin it. Otherwise
>
>Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>

Thanks, will do.


Regards,
-- 
Raghavendra Prabhu
GPG Id : 0xD72BE977
Fingerprint: B93F EBCB 8E05 7039 CD3C A4B8 A616 DCA1 D72B E977
www: wnohang.net

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

      reply	other threads:[~2012-10-24 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 18:58 [PATCH] Change the check for PageReadahead into an else-if raghu.prabhu13
2012-10-17  2:00 ` Fengguang Wu
2012-10-17  2:02   ` KOSAKI Motohiro
2012-10-24 20:44     ` Raghavendra D Prabhu [this message]

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=20121024204407.GA3218@Archie \
    --to=raghu.prabhu13@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=kosaki.motohiro@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=zheng.yan@oracle.com \
    /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).