From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@suse.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, qiuxishi@huawei.com,
linux-mm@kvack.org
Subject: Re: [RFC PATCH] mm: fix mlock incorrent event account
Date: Fri, 26 May 2017 11:57:57 +0800 [thread overview]
Message-ID: <5927A7C5.7070403@huawei.com> (raw)
In-Reply-To: <20170525141945.GK12721@dhcp22.suse.cz>
On 2017/5/25 22:19, Michal Hocko wrote:
> On Thu 25-05-17 21:48:56, zhong jiang wrote:
>> Hi Michal
>>
>> by a testcase, The patch is work as I think. The testcase is as follows.
>>
>> int main(void)
>> {
>> char *map;
>> int fd;
>>
>> fd = open("test", O_CREAT|O_RDWR);
>> unlink("test");
>> ftruncate(fd, 4096);
>> map = mmap(NULL, 4096, PROT_WRITE, MAP_PRIVATE, fd, 0);
>> map[0] = 11;
>> mlock(map, sizeof(fd));
> just a nit
> you probably wanted mlock(map, 4096)
>
>> ftruncate(fd, 0);
>> close(fd);
>> munlock(map, sizeof(fd));
> similarly here
>
>> munmap(map, 4096);
>>
>> return 0;
>> }
>>
>> before:
>> unevictable_pgs_mlocked 10589
>> unevictable_pgs_munlocked 10588
>> unevictable_pgs_cleared 1
>>
>> apply the patch;
>> after:
>> unevictable_pgs_mlocked 9497
>> unevictable_pgs_munlocked 9497
>> unevictable_pgs_cleared 1
> OK, this is definitely useful for the changelog.
>
>> unmap_mapping_range unmap them, page_remove_rmap will deal with
>> clear_page_mlock situation. we clear page Mlock flag and successful
>> isolate the page, the page will putback the evictable list. but it is not
>> record the munlock event.
> and this as well. I haven't checked that but it gives reviewers chance
> to understand your thinking much better so it is definitely useful.
> Mlock code is everything but straightforward.
>
HI, Michal
I will add the above info the chanelog. and resent it in v2.
Thanks
zhongjiang
--
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>
prev parent reply other threads:[~2017-05-26 3:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 7:59 zhongjiang
2017-05-25 8:13 ` Michal Hocko
2017-05-25 12:14 ` zhong jiang
2017-05-25 13:48 ` zhong jiang
2017-05-25 14:19 ` Michal Hocko
2017-05-26 3:57 ` zhong jiang [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=5927A7C5.7070403@huawei.com \
--to=zhongjiang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=qiuxishi@huawei.com \
--cc=vbabka@suse.cz \
/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