From: Petr Cermak <petrcermak-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
To: Namhyung Kim <namhyung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] proc.5: Add description of CLEAR_REFS_MM_HIWATER_RSS
Date: Thu, 8 Sep 2016 12:19:46 +0100 [thread overview]
Message-ID: <20160908111946.GA10605@google.com> (raw)
In-Reply-To: <20160907150439.21524-1-namhyung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, Sep 08, 2016 at 12:04:39AM +0900, Namhyung Kim wrote:
> The Linux kernel commit 695f05593693 ("fs/proc/task_mmu.c: add
> user-space support for resetting mm->hiwater_rss (peak RSS)") added a
> way to reset peak RSS of a process but missed to update manpage.
>
> Cc: Petr Cermak <petrcermak-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
> Signed-off-by: Namhyung Kim <namhyung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> ---
> man5/proc.5 | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/man5/proc.5 b/man5/proc.5
> index 14588fe..5cb3c85 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -352,6 +352,11 @@ by the check-point restore system to discover which pages of a process
> have been dirtied since the file
> .IR /proc/[pid]/clear_refs
> was written to.
> +.TP
> +5 (since Linux 4.0)
> +.\" Internally: CLEAR_REFS_MM_HIWATER_RSS
> +Reset the peak resident set size ("high water mark") to the process's
> +current value.
> .RE
> .IP
> Writing any value to
> --
> 2.9.3
>
Thanks for updating the documentation. I think you should also change
the line above from:
"A further value can be written to affect a different bit:"
to:
"Further values can be written to affect a different properties:"
Apart from that,
Acked-by: Petr Cermak <petrcermak-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-09-08 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 15:04 [PATCH] proc.5: Add description of CLEAR_REFS_MM_HIWATER_RSS Namhyung Kim
[not found] ` <20160907150439.21524-1-namhyung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-08 11:19 ` Petr Cermak [this message]
[not found] ` <20160908111946.GA10605-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2016-09-09 5:54 ` Namhyung Kim
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=20160908111946.GA10605@google.com \
--to=petrcermak-f7+t8e8rja9g9huczpvpmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=namhyung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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;
as well as URLs for NNTP newsgroup(s).