From: "xiaowen.liu@freescale.com" <xiaowen.liu@freescale.com>
To: "majordomo@kvack.org" <majordomo@kvack.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: rss MM_FILEPAGES statistics value issue in kernel memory remap_pfn_range function.
Date: Wed, 24 Sep 2014 09:55:56 +0000 [thread overview]
Message-ID: <e71eda4ca6734380876f0ddbb4e4f258@DM2PR03MB432.namprd03.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 734 bytes --]
Hi majordomo,
Sorry to bother you.
I noticed that there are two functions provided to map memory to user space from kernel: remap_pfn_range and vm_insert_page.
There is one difference that vm_insert_page increase task rss MM_FILEPAGES value. But remap_pfn_range doesn't.
The issue is the munmap function will call zap_pte_range to decrease task rss MM_FILEPAGES value.
So, the task rss MM_FILEPAGES value increase and decrease doesn't match.
And there are many places in kernel driver call remap_pfn_range to map memory to user space.
I think remap_pfn_range should also increase task rss MM_FILEPAGES value.
If there is any misunderstanding, please correct me.
Thanks.
BestRegards,
Ivan.liu
[-- Attachment #2: Type: text/html, Size: 4235 bytes --]
reply other threads:[~2014-09-24 9:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e71eda4ca6734380876f0ddbb4e4f258@DM2PR03MB432.namprd03.prod.outlook.com \
--to=xiaowen.liu@freescale.com \
--cc=linux-mm@kvack.org \
--cc=majordomo@kvack.org \
/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