From: Xishi Qiu <qiuxishi@huawei.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Yisheng Xie <xieyisheng1@huawei.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
zhongjiang <zhongjiang@huawei.com>
Subject: Re: [Question] Mlocked count will not be decreased
Date: Wed, 24 May 2017 20:10:54 +0800 [thread overview]
Message-ID: <5925784E.802@huawei.com> (raw)
In-Reply-To: <d354b321-0d11-4308-0b0e-aacef5a5e34b@suse.cz>
On 2017/5/24 19:52, Vlastimil Babka wrote:
> On 05/24/2017 01:38 PM, Xishi Qiu wrote:
>>>
>>> Race condition with what? Who else would isolate our pages?
>>>
>>
>> Hi Vlastimil,
>>
>> I find the root cause, if the page was not cached on the current cpu,
>> lru_add_drain() will not push it to LRU. So we should handle fail
>> case in mlock_vma_page().
>
> Yeah that would explain it.
>
>> follow_page_pte()
>> ...
>> if (page->mapping && trylock_page(page)) {
>> lru_add_drain(); /* push cached pages to LRU */
>> /*
>> * Because we lock page here, and migration is
>> * blocked by the pte's page reference, and we
>> * know the page is still mapped, we don't even
>> * need to check for file-cache page truncation.
>> */
>> mlock_vma_page(page);
>> unlock_page(page);
>> }
>> ...
>>
>> I think we should add yisheng's patch, also we should add the following change.
>> I think it is better than use lru_add_drain_all().
>
> I agree about yisheng's fix (but v2 didn't address my comments). I don't
> think we should add the hunk below, as that deviates from the rest of
> the design.
Hi Vlastimil,
The rest of the design is that mlock should always success here, right?
If we don't handle the fail case, the page will be in anon/file lru list
later when call __pagevec_lru_add(), but NR_MLOCK increased,
this is wrong, right?
Thanks,
Xishi Qiu
>
> Thanks,
> Vlastimil
>
>> diff --git a/mm/mlock.c b/mm/mlock.c
>> index 3d3ee6c..ca2aeb9 100644
>> --- a/mm/mlock.c
>> +++ b/mm/mlock.c
>> @@ -88,6 +88,11 @@ void mlock_vma_page(struct page *page)
>> count_vm_event(UNEVICTABLE_PGMLOCKED);
>> if (!isolate_lru_page(page))
>> putback_lru_page(page);
>> + else {
>> + ClearPageMlocked(page);
>> + mod_zone_page_state(page_zone(page), NR_MLOCK,
>> + -hpage_nr_pages(page));
>> + }
>> }
>> }
>>
>> Thanks,
>> Xishi Qiu
>>
>
>
> .
>
--
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-05-24 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 14:41 Kefeng Wang
2017-05-23 22:04 ` Tetsuo Handa
2017-05-24 8:32 ` Yisheng Xie
2017-05-24 8:57 ` Kefeng Wang
2017-05-24 10:32 ` Vlastimil Babka
2017-05-24 10:42 ` Vlastimil Babka
2017-05-24 10:49 ` Xishi Qiu
2017-05-24 11:38 ` Xishi Qiu
2017-05-24 11:52 ` Vlastimil Babka
2017-05-24 12:10 ` Xishi Qiu [this message]
2017-05-24 13:16 ` Vlastimil Babka
2017-05-25 1:16 ` Xishi Qiu
2017-05-25 6:12 ` Vlastimil Babka
2017-05-25 1:00 ` Yisheng Xie
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=5925784E.802@huawei.com \
--to=qiuxishi@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=xieyisheng1@huawei.com \
--cc=zhongjiang@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