From: David Rientjes <rientjes@google.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Davide Libenzi <davidel@xmailserver.org>,
Luiz Capitulino <lcapitulino@redhat.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Joern Engel <joern@logfs.org>, Jianguo Wu <wujianguo@huawei.com>,
Eric B Munson <emunson@akamai.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [patch 1/2] mm, doc: cleanup and clarify munmap behavior for hugetlb memory
Date: Thu, 2 Apr 2015 15:40:56 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1504021536210.15536@chino.kir.corp.google.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1503291801400.1052@eggly.anvils>
On Sun, 29 Mar 2015, Hugh Dickins wrote:
> > munmap(2) of hugetlb memory requires a length that is hugepage aligned,
> > otherwise it may fail. Add this to the documentation.
>
> Thanks for taking this on, David. But although munmap(2) is the one
> Davide called out, it goes beyond that, doesn't it? To mprotect and
> madvise and ...
>
Yes, good point, munmap(2) isn't special in this case, the alignment to
the native page size of the platform should apply to madvise, mbind,
mincore, mlock, mprotect, remap_file_pages, etc.
I'd hesitate to compile any authoritative list on the behavior in
Documentation/vm/hugetlbpage.txt since it would exclude future extensions,
but I'll update it to be more inclusive of other mm syscalls rather than
specify only munmap(2).
--
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:[~2015-04-02 22:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 23:23 David Rientjes
2015-03-26 23:23 ` [patch 2/2] mm, selftests: test return value of munmap for MAP_HUGETLB memory David Rientjes
2015-03-26 23:52 ` Michael Ellerman
2015-03-27 13:58 ` [patch 1/2] mm, doc: cleanup and clarify munmap behavior for hugetlb memory Eric B Munson
2015-03-28 1:37 ` David Rientjes
2015-03-30 1:35 ` Hugh Dickins
2015-03-30 14:23 ` Eric B Munson
2015-03-30 20:23 ` Hugh Dickins
2015-04-02 22:40 ` David Rientjes [this message]
2015-04-02 22:50 ` [patch -mm] mm, doc: cleanup and clarify munmap behavior for hugetlb memory fix David Rientjes
2015-04-03 1:05 ` Hugh Dickins
2015-04-04 9:34 ` Jonathan Corbet
2015-04-09 19:46 ` David Rientjes
2015-04-11 13:26 ` Jonathan Corbet
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=alpine.DEB.2.10.1504021536210.15536@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davidel@xmailserver.org \
--cc=emunson@akamai.com \
--cc=hughd@google.com \
--cc=joern@logfs.org \
--cc=lcapitulino@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuahkh@osg.samsung.com \
--cc=wujianguo@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