From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: <chenhao36@huawei.com>
Subject: Re: [f2fs-dev] [PATCH 1/7] f2fs: avoid needless lock for node pages when fsyncing a file
Date: Tue, 26 Apr 2016 20:51:04 +0800 [thread overview]
Message-ID: <d9af7096-871c-9686-4221-e43c32bf6d10@huawei.com> (raw)
In-Reply-To: <1461629220-16280-1-git-send-email-jaegeuk@kernel.org>
Hi Jaegeuk,
On 2016/4/26 8:06, Jaegeuk Kim wrote:
> When fsync is called, sync_node_pages finds a proper direct node pages to flush.
> But, it locks unrelated direct node pages together unnecessarily.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
I've reviewed this patchset, it looks good to me, please add:
Acked-by: Chao Yu <yuchao0@huawei.com>
prev parent reply other threads:[~2016-04-26 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:06 Jaegeuk Kim
2016-04-26 0:06 ` [PATCH 2/7] f2fs: avoid writing 0'th page in volatile writes Jaegeuk Kim
2016-04-26 0:06 ` [PATCH 3/7] f2fs: split sync_node_pages with fsync_node_pages Jaegeuk Kim
2016-04-26 0:06 ` [PATCH 4/7] f2fs: report unwritten status in fsync_node_pages Jaegeuk Kim
2016-04-26 0:06 ` [PATCH 5/7] f2fs: set fsync mark only for the last dnode Jaegeuk Kim
2016-04-26 0:06 ` [PATCH 6/7] f2fs: issue cache flush on direct IO Jaegeuk Kim
2016-04-26 0:07 ` [PATCH 7/7] f2fs: should check the remaining dentry bits Jaegeuk Kim
2016-04-26 2:53 ` [PATCH v2 " Jaegeuk Kim
2016-04-27 14:22 ` [f2fs-dev] [PATCH " Chao Yu
2016-04-27 17:40 ` Jaegeuk Kim
2016-04-26 12:51 ` Chao Yu [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=d9af7096-871c-9686-4221-e43c32bf6d10@huawei.com \
--to=yuchao0@huawei.com \
--cc=chenhao36@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®