linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <agl@google.com>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, alangley@gmail.com
Subject: [PATCH] madvise.2: MADV_WIPEONFORK affects semantics
Date: Tue, 28 Apr 2020 17:40:26 +0000	[thread overview]
Message-ID: <000000000000b27fc105a45d533e@google.com> (raw)

Include MADV_WIPEONFORK in the list of advice values that have a
semantic impact on the calling process.
---
  man2/madvise.2 | 4 +++-
  1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/man2/madvise.2 b/man2/madvise.2
index a0f3a477a..6c25f697a 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -84,21 +84,23 @@ values have been added.
  The
  .I advice
  values listed below
  allow an application to tell the kernel how it expects to use
  some mapped or shared memory areas, so that the kernel can choose
  appropriate read-ahead and caching techniques.
  These
  .I advice
  values do not influence the semantics of the application
  (except in the case of
-.BR MADV_DONTNEED ),
+.BR MADV_DONTNEED
+and
+.BR MADV_WIPEONFORK ),
  but may influence its performance.
  All of the
  .I advice
  values listed here have analogs in the POSIX-specified
  .BR posix_madvise (3)
  function, and the values have the same meanings, with the exception of
  .BR MADV_DONTNEED .
  .PP
  The advice is indicated in the
  .I advice
-- 
2.26.0


             reply	other threads:[~2020-04-28 17:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 17:40 agl [this message]
2020-04-28 18:09 ` [PATCH] madvise.2: MADV_WIPEONFORK affects semantics Jakub Wilk
2020-04-29  6:09   ` Michael Kerrisk (man-pages)
2020-04-29 13:47   ` Adam Langley

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=000000000000b27fc105a45d533e@google.com \
    --to=agl@google.com \
    --cc=alangley@gmail.com \
    --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).