From: Michal Hocko <mhocko@kernel.org>
To: zhouxianrong@huawei.com
Cc: viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, zhouxiyu@huawei.com, wanghaijun5@huawei.com,
yuchao0@huawei.com
Subject: Re: [PATCH] reusing of mapping page supplies a way for file page allocation under low memory due to pagecache over size and is controlled by sysctl parameters. it is used only for rw page allocation rather than fault or readahead allocation. it is like relclaim but is lighter than reclaim. it only reuses clean and zero mapcount pages of mapping. for special filesystems using this feature like below:
Date: Tue, 31 May 2016 11:36:31 +0200 [thread overview]
Message-ID: <20160531093631.GH26128@dhcp22.suse.cz> (raw)
In-Reply-To: <1464685702-100211-1-git-send-email-zhouxianrong@huawei.com>
On Tue 31-05-16 17:08:22, zhouxianrong@huawei.com wrote:
> From: z00281421 <z00281421@notesmail.huawei.com>
>
> const struct address_space_operations special_aops = {
> ...
> .reuse_mapping_page = generic_reuse_mapping_page,
> }
Please try to write a proper changelog which explains what is the
change, why do we need it and who is it going to use.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-05-31 9:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 9:08 zhouxianrong
2016-05-31 9:36 ` Michal Hocko [this message]
2016-05-31 13:35 ` 答复: [PATCH] reusing of mapping page supplies a way for file page allocation under low memory due to pagecache over size and is controlled by sysctl parameters. it is used only for rw page allocation rather than fault or readahead allocation. it is like zhouxianrong
2016-05-31 14:03 ` Michal Hocko
2016-06-01 1:52 ` zhouxianrong
2016-06-01 8:18 ` Michal Hocko
2016-06-01 9:06 ` zhouxianrong
2016-06-01 9:49 ` Michal Hocko
2016-06-01 9:56 ` zhouxianrong
2016-06-01 9:28 ` zhouxianrong
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=20160531093631.GH26128@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wanghaijun5@huawei.com \
--cc=yuchao0@huawei.com \
--cc=zhouxianrong@huawei.com \
--cc=zhouxiyu@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