From: Kirill Smelkov <kirr@nexedi.com>
To: mtk.manpages@gmail.com
Cc: Kirill Smelkov <kirr@nexedi.com>,
linux-man@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [patch] mmap.2: Add link to commit which broke MAP_POPULATE | MAP_NONBLOCK to be noop
Date: Sat, 18 Mar 2017 22:40:10 +0300 [thread overview]
Message-ID: <20170318194010.11639-1-kirr@nexedi.com> (raw)
Signed-off-by: Kirill Smelkov <kirr@nexedi.com>
---
man2/mmap.2 | 1 +
1 file changed, 1 insertion(+)
diff --git a/man2/mmap.2 b/man2/mmap.2
index 96875e486..f6fd56523 100644
--- a/man2/mmap.2
+++ b/man2/mmap.2
@@ -300,6 +300,7 @@ Don't perform read-ahead:
create page tables entries only for pages
that are already present in RAM.
Since Linux 2.6.23, this flag causes
+.\" commit 54cb8821de07f2ffcd28c380ce9b93d5784b40d7
.BR MAP_POPULATE
to do nothing.
One day, the combination of
--
2.11.0
next reply other threads:[~2017-03-18 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 19:40 Kirill Smelkov [this message]
2017-03-20 15:59 ` Why mmap(MAP_POPULATE | MAP_NONBLOCK) is needed (Re: [patch] mmap.2: Add link to commit which broke MAP_POPULATE | MAP_NONBLOCK to be noop) Kirill Smelkov
2017-03-20 19:38 ` Michael Kerrisk (man-pages)
2017-03-20 20:06 ` Kirill Smelkov
2017-04-19 8:22 ` Kirill Smelkov
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=20170318194010.11639-1-kirr@nexedi.com \
--to=kirr@nexedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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).