linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Sahrawat <amit.sahrawat83@gmail.com>
To: Namjae Jeon <linkinjeon@gmail.com>
Cc: viro@zeniv.linux.org.uk, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs : remove unneeded plug in mpage_readpages.
Date: Thu, 17 Nov 2011 14:22:52 +0530	[thread overview]
Message-ID: <CADDb1s3fNxeXOvGZOUUK5Vjr5TLRTLn8mHezA8tc0u_JX7+ErQ@mail.gmail.com> (raw)
In-Reply-To: <1321026853-16388-1-git-send-email-linkinjeon@gmail.com>

Any feedback for this patch?

Thanks & Regards,
Amit Sahrawat

On Fri, Nov 11, 2011 at 9:24 PM, Namjae Jeon <linkinjeon@gmail.com> wrote:
> block plug in mpage_readpages is duplicated with plug of read_pages. So block plug is not needed in mpage_readpages.
>
> Signed-off-by: Namjae Jeon <linkinjeon@gmail.com>
> Signed-off-by: Amit Sahrawat <amit.sahrawat83@gmail.com>
> ---
>  fs/mpage.c |    4 ----
>  1 files changed, 0 insertions(+), 4 deletions(-)
>
> diff --git a/fs/mpage.c b/fs/mpage.c
> index fdfae9f..643e9f5 100644
> --- a/fs/mpage.c
> +++ b/fs/mpage.c
> @@ -371,9 +371,6 @@ mpage_readpages(struct address_space *mapping, struct list_head *pages,
>        sector_t last_block_in_bio = 0;
>        struct buffer_head map_bh;
>        unsigned long first_logical_block = 0;
> -       struct blk_plug plug;
> -
> -       blk_start_plug(&plug);
>
>        map_bh.b_state = 0;
>        map_bh.b_size = 0;
> @@ -395,7 +392,6 @@ mpage_readpages(struct address_space *mapping, struct list_head *pages,
>        BUG_ON(!list_empty(pages));
>        if (bio)
>                mpage_bio_submit(READ, bio);
> -       blk_finish_plug(&plug);
>        return 0;
>  }
>  EXPORT_SYMBOL(mpage_readpages);
> --
> 1.7.4.4
>
>

      reply	other threads:[~2011-11-17  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 15:54 [PATCH] fs : remove unneeded plug in mpage_readpages Namjae Jeon
2011-11-17  8:52 ` Amit Sahrawat [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=CADDb1s3fNxeXOvGZOUUK5Vjr5TLRTLn8mHezA8tc0u_JX7+ErQ@mail.gmail.com \
    --to=amit.sahrawat83@gmail.com \
    --cc=linkinjeon@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).