From: Chao Yu <chao@kernel.org>
To: guoweichao <guoweichao@huawei.com>,
yuchao0@huawei.com, linux-f2fs-devel@lists.sourceforge.net,
jaegeuk@kernel.org
Cc: huxinwei@huawei.com
Subject: Re: [PATCH v2] F2FS customized migrate_page callback
Date: Tue, 20 Sep 2016 23:02:27 +0800 [thread overview]
Message-ID: <f2a6a678-d87d-13ea-da6e-f131fc676d31@kernel.org> (raw)
In-Reply-To: <50788fd8-bbe0-706a-d31f-7b7ab99171c7@huawei.com>
On 2016/9/20 10:20, guoweichao wrote:
> No, the 'page_count' of the old/new page for Page Cache has been maintained in 'migrate_page_move_mapping'. As atomic-written pages have an additional reference, we should update their 'page_count' here.
Got it. Now, this patch looks good to me. :)
Reviewed-by: Chao Yu <yuchao0@huawei.com>
------------------------------------------------------------------------------
prev parent reply other threads:[~2016-09-20 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 21:03 [PATCH v2] F2FS customized migrate_page callback Weichao Guo
2016-09-19 14:48 ` Chao Yu
2016-09-20 2:20 ` guoweichao
2016-09-20 15:02 ` 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=f2a6a678-d87d-13ea-da6e-f131fc676d31@kernel.org \
--to=chao@kernel.org \
--cc=guoweichao@huawei.com \
--cc=huxinwei@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=yuchao0@huawei.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).