[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170926091837.fqvsurdvzapvlomu@dhcp22.suse.cz>
Date: Tue, 26 Sep 2017 11:18:37 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Xishi Qiu <qiuxishi@...wei.com>
Cc: Joonsoo Kim <iamjoonsoo.kim@....com>,
Vlastimil Babka <vbabka@...e.cz>,
Mel Gorman <mgorman@...hsingularity.net>,
Linux MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
zhong jiang <zhongjiang@...wei.com>,
yeyunfeng <yeyunfeng@...wei.com>, wanghaitao12@...wei.com,
"Zhoukang (A)" <zhoukang7@...wei.com>
Subject: Re: [RFC] a question about mlockall() and mprotect()
On Tue 26-09-17 17:13:59, Xishi Qiu wrote:
> On 2017/9/26 17:02, Michal Hocko wrote:
[...]
> > This is still very fuzzy. What are you actually trying to achieve?
>
> I don't expect page fault any more after mlock.
This should be the case normally. Except when mm_populate fails which
can happen e.g. when running inside a memcg with the hard limit
configured. Is there any other unexpected failure scenario you are
seeing?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists