From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: zhong jiang <zhongjiang@huawei.com>
Cc: kirill.shutemov@linux.intel.com, Mel Gorman <mgorman@suse.de>,
Michal Hocko <mhocko@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: A question about transparent hugepages
Date: Thu, 4 Aug 2016 12:16:01 +0300 [thread overview]
Message-ID: <20160804091601.GA12395@node.shutemov.name> (raw)
In-Reply-To: <57A2BE55.1020302@huawei.com>
On Thu, Aug 04, 2016 at 12:02:29PM +0800, zhong jiang wrote:
> according to the total_mapcount, Different process can map any subpages of the
> transparent hugepages. How it can happen to ?
For anonymous memory it can only happen over copy-on-write via fork() +
munmap() or something in one of the processes.
Now we have tmpfs/shmem with huge pages in mainline. In this case you can
map any subpage directly from file.
--
Kirill A. Shutemov
prev parent reply other threads:[~2016-08-04 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 4:02 A question about transparent hugepages zhong jiang
2016-08-04 9:16 ` Kirill A. Shutemov [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=20160804091601.GA12395@node.shutemov.name \
--to=kirill@shutemov.name \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--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