From: Jakub Wilk <jwilk@jwilk.net>
To: Adam Langley <agl@google.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
<linux-man@vger.kernel.org>, <alangley@gmail.com>
Subject: Re: [PATCH] madvise.2: MADV_WIPEONFORK affects semantics
Date: Tue, 28 Apr 2020 20:09:42 +0200 [thread overview]
Message-ID: <20200428180942.qwjjmp2e5sbx3opn@jwilk.net> (raw)
In-Reply-To: <000000000000b27fc105a45d533e@google.com>
Hi Adam!
* Adam Langley <agl@google.com>, 2020-04-28, 17:40:
> 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.
This sentence is in the "Conventional advice value" subsection, which
defines only MADV_NORMAL, MADV_RANDOM, MADV_SEQUENTIAL, MADV_WILLNEED,
and MADV_DONTNEED.
MADV_WIPEONFORK is defined in the "Linux-specific advice values"
subsection, which already notes that "some of these operations change
the semantics of memory accesses". (Perhaps s/some/most/ would be better
wording.)
--
Jakub Wilk
next prev parent reply other threads:[~2020-04-28 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 17:40 [PATCH] madvise.2: MADV_WIPEONFORK affects semantics agl
2020-04-28 18:09 ` Jakub Wilk [this message]
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=20200428180942.qwjjmp2e5sbx3opn@jwilk.net \
--to=jwilk@jwilk.net \
--cc=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).