From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mhocko@kernel.org
Cc: mtk.manpages@gmail.com, linux-mm@kvack.org,
"Niklas Hambüchen" <mail@nh2.me>, "Shaohua Li" <shli@fb.com>,
linux-man@vger.kernel.org, "Michal Hocko" <mhocko@suse.com>
Subject: Re: [PATCH] madvise.2: MADV_FREE clarify swapless behavior
Date: Sat, 1 Dec 2018 09:54:32 +0100 [thread overview]
Message-ID: <79858664-94a8-0b32-f8f0-866c018d7b20@gmail.com> (raw)
In-Reply-To: <20181129181048.11010-1-mhocko@kernel.org>
On 11/29/18 7:10 PM, mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> Since 93e06c7a6453 ("mm: enable MADV_FREE for swapless system") we
> handle MADV_FREE on a swapless system the same way as with the swap
> available. Clarify that fact in the man page.
Thanks, Michal (and Niklas). Patch applied.
Cheers,
Michael
> Reported-by: Niklas Hambüchen <mail@nh2.me>
> ---
> man2/madvise.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/madvise.2 b/man2/madvise.2
> index eb82a57a1cf5..d9135a05a1c2 100644
> --- a/man2/madvise.2
> +++ b/man2/madvise.2
> @@ -403,7 +403,7 @@ The
> operation
> can be applied only to private anonymous pages (see
> .BR mmap (2)).
> -On a swapless system, freeing pages in a given range happens instantly,
> +Prior to 4.12 on a swapless system, freeing pages in a given range happens instantly,
> regardless of memory pressure.
> .TP
> .BR MADV_WIPEONFORK " (since Linux 4.14)"
>
--
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:[~2018-12-01 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:10 mhocko
2018-12-01 8:54 ` 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=79858664-94a8-0b32-f8f0-866c018d7b20@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mail@nh2.me \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=shli@fb.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