From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/3] proc.5: cfix
Date: Sun, 04 May 2014 07:41:59 +0200 [thread overview]
Message-ID: <5365D327.3010002@gmail.com> (raw)
In-Reply-To: <1399166675-16019-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Hi David,
Including the ':' was intended. Why did you want to remove it?
Cheers,
Michael
On 05/04/2014 03:24 AM, David Prévot wrote:
> ---
> man5/proc.5 | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/man5/proc.5 b/man5/proc.5
> index be6b755..123bc8f 100644
> --- a/man5/proc.5
> +++ b/man5/proc.5
> @@ -155,14 +155,14 @@ bits for all file-mapped pages associated with the process.
> .IP
> Clearing the PG_Referenced and ACCESSED/YOUNG bits provides a method
> to measure approximately how much memory a process is using.
> -One first inspects the values in the "Referenced:" fields
> +One first inspects the values in the "Referenced" fields
> for the VMAs shown in
> .IR /proc/[pid]/smaps
> to get an idea of the memory footprint of the
> process.
> One then clears the PG_Referenced and ACCESSED/YOUNG bits
> and, after some measured time interval,
> -once again inspects the values in the "Referenced:" fields
> +once again inspects the values in the "Referenced" fields
> to get an idea of the change in memory footprint of the
> process during the measured interval.
> If one is interested only in inspecting the selected mapping types,
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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:[~2014-05-04 5:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 1:24 [PATCH 1/3] proc.5: cfix David Prévot
[not found] ` <1399166675-16019-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-05-04 1:24 ` [PATCH 2/3] inet.3: tfix David Prévot
[not found] ` <1399166675-16019-2-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-05-04 5:43 ` Michael Kerrisk (man-pages)
2014-05-04 1:24 ` [PATCH 3/3] inet_net_pton.3: wfix David Prévot
[not found] ` <1399166675-16019-3-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-05-04 5:45 ` Michael Kerrisk (man-pages)
2014-05-04 5:41 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <5365D327.3010002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-05-04 23:04 ` [PATCH 1/3] proc.5: cfix David Prévot
[not found] ` <5366C77A.60901-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2014-05-05 6:26 ` Michael Kerrisk (man-pages)
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=5365D327.3010002@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=taffit-8fiUuRrzOP0dnm+yROfE0A@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).