From: Shaohua Li <shaohua.li@intel.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: Ted Ts'o <tytso@mit.edu>, Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: [patch]ext4: add block plug for .writepages
Date: Wed, 12 Oct 2011 08:53:01 +0800 [thread overview]
Message-ID: <1318380781.22361.98.camel@sli10-conroe> (raw)
In-Reply-To: <CAH9JG2X9Hik6Qs8BHKS1WqJmiB9=Ve-W0XiZ+-dfHFnN1GmXKg@mail.gmail.com>
On Tue, 2011-10-11 at 18:40 +0800, Kyungmin Park wrote:
> On Tue, Oct 11, 2011 at 1:51 AM, Ted Ts'o <tytso@mit.edu> wrote:
> > On Wed, Sep 28, 2011 at 11:09:40AM +0800, Shaohua Li wrote:
> >> I searched a little bit, looks only ext4 need it. here is the patch.
> >>
> >>
> >> Add block plug for ext4 .writepages. Though ext4 .writepages
> >> already handles request merge very well, block plug is still
> >> helpful to reduce block lock contention.
> >>
> >> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
>
> Does it require to add blk_finish_plug(&plug) when error case?
oops, we need.
Subject: ext4: calling blk_finish_plug in error path
Forgot calling blk_finish_plug in error code path. Thanks Kyungmin Park pointed
it out.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
---
fs/ext4/inode.c | 1 +
1 file changed, 1 insertion(+)
Index: linux/fs/ext4/inode.c
===================================================================
--- linux.orig/fs/ext4/inode.c 2011-10-12 08:46:32.000000000 +0800
+++ linux/fs/ext4/inode.c 2011-10-12 08:48:10.000000000 +0800
@@ -2144,6 +2144,7 @@ retry:
ext4_msg(inode->i_sb, KERN_CRIT, "%s: jbd2_start: "
"%ld pages, ino %lu; err %d", __func__,
wbc->nr_to_write, inode->i_ino, ret);
+ blk_finish_plug(&plug);
goto out_writepages;
}
prev parent reply other threads:[~2011-10-12 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1317004226.29510.172.camel@sli10-conroe>
[not found] ` <20110926073025.GB21079@infradead.org>
[not found] ` <1317022727.29510.175.camel@sli10-conroe>
[not found] ` <20110926094554.GA30827@infradead.org>
2011-09-28 3:09 ` [patch]ext4: add block plug for .writepages Shaohua Li
2011-10-09 6:09 ` Shaohua Li
2011-10-10 16:51 ` Ted Ts'o
2011-10-11 0:07 ` NamJae Jeon
2011-10-11 10:40 ` Kyungmin Park
2011-10-12 0:53 ` Shaohua Li [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=1318380781.22361.98.camel@sli10-conroe \
--to=shaohua.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kmpark@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).