From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Bruce Merry <bmerry@ska.ac.za>,
linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-mm@kvack.org
Subject: Re: [patch] Clarify that MAP_POPULATE is best-effort
Date: Sun, 4 Apr 2021 21:28:57 +0200 [thread overview]
Message-ID: <36f6ac8a-e746-5546-5354-35b86dcff4ca@gmail.com> (raw)
In-Reply-To: <20210323074831.GA7535@kryton.kat.ac.za>
Hello Bruce,
On 3/23/21 8:48 AM, Bruce Merry wrote:
> As discussed on linux-mm
> (https://marc.info/?l=linux-mm&m=161528594100612&w=2), MAP_POPULATE can
> fail silently if the hugetlb cgroup settings allow huge page reservation
> but prevents huge pages being allocated.
>
> Closes https://bugzilla.kernel.org/show_bug.cgi?id=212153.
> ---
> man2/mmap.2 | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/man2/mmap.2 b/man2/mmap.2
> index 164ba196e..03f2eeb2c 100644
> --- a/man2/mmap.2
> +++ b/man2/mmap.2
> @@ -400,6 +400,11 @@ private writable mappings.
> Populate (prefault) page tables for a mapping.
> For a file mapping, this causes read-ahead on the file.
> This will help to reduce blocking on page faults later.
> +The
> +.BR mmap ()
> +call doesn't fail if the mapping cannot be populated (for example, due
> +to limitations on the number of mapped huge pages when using
> +.BR MAP_HUGETLB ).
> .BR MAP_POPULATE
> is supported for private mappings only since Linux 2.6.23.
> .TP
Thanks. Patch applied.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2021-04-04 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 7:48 Bruce Merry
2021-04-04 19:28 ` Michael Kerrisk (man-pages) [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=36f6ac8a-e746-5546-5354-35b86dcff4ca@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=bmerry@ska.ac.za \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@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