From: Vlastimil Babka <vbabka@suse.cz>
To: Xishi Qiu <qiuxishi@huawei.com>, Michal Hocko <mhocko@kernel.org>
Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Mel Gorman <mgorman@techsingularity.net>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
zhong jiang <zhongjiang@huawei.com>,
yeyunfeng <yeyunfeng@huawei.com>,
wanghaitao12@huawei.com, "Zhoukang (A)" <zhoukang7@huawei.com>
Subject: Re: [RFC] a question about mlockall() and mprotect()
Date: Tue, 26 Sep 2017 11:45:16 +0200 [thread overview]
Message-ID: <6b38ed08-62cb-97b1-9f16-1fd8e272b137@suse.cz> (raw)
In-Reply-To: <59CA1C6E.4010501@huawei.com>
On 09/26/2017 11:22 AM, Xishi Qiu wrote:
> On 2017/9/26 17:13, Xishi Qiu wrote:
>>> This is still very fuzzy. What are you actually trying to achieve?
>>
>> I don't expect page fault any more after mlock.
>>
>
> Our apps is some thing like RT, and page-fault maybe cause a lot of time,
> e.g. lock, mem reclaim ..., so I use mlock and don't want page fault
> any more.
Why does your app then have restricted mprotect when calling mlockall()
and only later adjusts the mprotect?
Vlastimil
--
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:[~2017-09-26 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 7:56 Xishi Qiu
2017-09-26 8:17 ` Michal Hocko
2017-09-26 8:39 ` Xishi Qiu
2017-09-26 9:02 ` Michal Hocko
2017-09-26 9:13 ` Xishi Qiu
2017-09-26 9:18 ` Michal Hocko
2017-09-26 9:22 ` Xishi Qiu
2017-09-26 9:45 ` Vlastimil Babka [this message]
2017-09-26 11:00 ` Michal Hocko
2017-09-27 5:51 ` Xishi Qiu
2017-10-09 18:26 ` Michal Hocko
2017-10-10 1:22 ` Xishi Qiu
2017-10-10 5:50 ` Michal Hocko
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=6b38ed08-62cb-97b1-9f16-1fd8e272b137@suse.cz \
--to=vbabka@suse.cz \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=wanghaitao12@huawei.com \
--cc=yeyunfeng@huawei.com \
--cc=zhongjiang@huawei.com \
--cc=zhoukang7@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