From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: David Rientjes <rientjes@google.com>,
Mike Kravetz <mike.kravetz@oracle.com>
Cc: mtk.manpages@gmail.com, Hugh Dickins <hughd@google.com>,
Davide Libenzi <davidel@xmailserver.org>,
Eric B Munson <emunson@akamai.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-man@vger.kernel.org
Subject: Re: [patch] mmap.2: document the munmap exception for underlying page size
Date: Thu, 23 Jul 2015 15:15:44 +0200 [thread overview]
Message-ID: <55B0E900.8090207@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1507221646100.14953@chino.kir.corp.google.com>
On 07/23/2015 01:49 AM, David Rientjes wrote:
> On Wed, 22 Jul 2015, Mike Kravetz wrote:
>
>> On 07/21/2015 05:41 PM, David Rientjes wrote:
>>> munmap(2) will fail with an errno of EINVAL for hugetlb memory if the
>>> length is not a multiple of the underlying page size.
>>>
>>> Documentation/vm/hugetlbpage.txt was updated to specify this behavior
>>> since Linux 4.1 in commit 80d6b94bd69a ("mm, doc: cleanup and clarify
>>> munmap behavior for hugetlb memory").
>>>
>>> Signed-off-by: David Rientjes <rientjes@google.com>
>>> ---
>>> man2/mmap.2 | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/man2/mmap.2 b/man2/mmap.2
>>> --- a/man2/mmap.2
>>> +++ b/man2/mmap.2
>>> @@ -383,6 +383,10 @@ All pages containing a part
>>> of the indicated range are unmapped, and subsequent references
>>> to these pages will generate
>>> .BR SIGSEGV .
>>> +An exception is when the underlying memory is not of the native page
>>> +size, such as hugetlb page sizes, whereas
>>> +.I length
>>> +must be a multiple of the underlying page size.
>>> It is not an error if the
>>> indicated range does not contain any mapped pages.
>>> .SS Timestamps changes for file-backed mappings
>>>
>>> --
>>
>> Should we also add a similar comment for the mmap offset? Currently
>> the man page says:
>>
>> "offset must be a multiple of the page size as returned by
>> sysconf(_SC_PAGE_SIZE)."
>>
>> For hugetlbfs, I beieve the offset must be a multiple of the
>> hugetlb page size. A similar comment/exception about using
>> the "underlying page size" would apply here as well.
>>
>
> Yes, that makes sense, thanks. We should also explicitly say that mmap(2)
> automatically aligns length to be hugepage aligned if backed by hugetlbfs.
And, surely, it also does something similar for mmap()'s 'addr'
argument?
I suggest we add a subsection to describe the HugeTLB differences. How
about something like:
Huge page (Huge TLB) mappings
For mappings that employ huge pages, the requirements for the
arguments of mmap() and munmap() differ somewhat from the
requirements for mappings that use the native system page size.
For mmap(), offset must be a multiple of the underlying huge page
size. The system automatically aligns length to be a multiple of
the underlying huge page size.
For munmap(), addr and length must both be a multiple of the
underlying huge page size.
?
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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-07-23 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 0:41 [patch] mmap.2: document the munmap exception for underlying page size David Rientjes
2015-07-22 17:16 ` Michael Kerrisk (man-pages)
2015-07-22 22:03 ` David Rientjes
2015-07-23 13:05 ` Michael Kerrisk (man-pages)
2015-07-22 23:31 ` Mike Kravetz
2015-07-22 23:49 ` David Rientjes
2015-07-23 13:15 ` Michael Kerrisk (man-pages) [this message]
2015-07-23 20:52 ` David Rientjes
2015-07-24 6:57 ` Michael Kerrisk (man-pages)
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=55B0E900.8090207@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=davidel@xmailserver.org \
--cc=emunson@akamai.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).