From: Mijo Safradin <safradin-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Jan Chaloupka <jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] proc.5: Add missing fields to /proc/PID/stat
Date: Thu, 10 Jul 2014 12:24:14 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1407101216210.30830@tp530.de.ibm.com> (raw)
In-Reply-To: <53BE5E17.8050509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hi Jan,
ok, thanks.
Mijo
On Thu, 10 Jul 2014, Jan Chaloupka wrote:
> Hi, Mijo,
>
> the patch is already sent
>
> http://www.spinics.net/lists/linux-man/msg06029.html
>
> Just not pushed to the repo.
>
> Jan
>
> On 07/10/2014 11:10 AM, Mijo Safradin wrote:
>> Merge stat fields from upstream file 'fs/proc/array.c'
>>
>> Fields to add:
>> 'start_data', 'end_data', 'start_brk', 'arg_start',
>> 'arg_end', 'env_start', 'env_end', 'exit_code'
>> ---
>> man5/proc.5 | 25 +++++++++++++++++++++++++
>> 1 file changed, 25 insertions(+)
>>
>> diff --git a/man5/proc.5 b/man5/proc.5
>> index 239d8ac..617c20a 100644
>> --- a/man5/proc.5
>> +++ b/man5/proc.5
>> @@ -1383,6 +1383,31 @@ for a guest operating system), measured in clock
>> ticks (divide by
>> \fIcguest_time\fP %ld (since Linux 2.6.24)
>> (44) Guest time of the process's children, measured in clock ticks
>> (divide by
>> .IR sysconf(_SC_CLK_TCK) ).
>> +.TP
>> +\fIstartdata\fP %lu
>> +(45) address above which program data+bss is placed.
>> +.TP
>> +\fIenddata\fP %lu
>> +(46) address below which program data+bss is placed.
>> +.TP
>> +\fIstartbrk\fP %lu
>> +(47) address above which program heap can be expanded with brk().
>> +.TP
>> +\fIargstart\fP %lu
>> +(48) address above which program command line is placed.
>> +.TP
>> +\fIargend\fP %lu
>> +(49) address below which program command line is placed.
>> +.TP
>> +\fIenvstart\fP %lu
>> +(50) address above which program environment is placed.
>> +.TP
>> +\fIenvend\fP %lu
>> +(51) address below which program environment is placed.
>> +.TP
>> +\fIexitcode\fP %lu
>> +(52) the thread's exit_code in the form reported by the waitpid system
>> call.
>> +.TP
>> .RE
>> .TP
>> .I /proc/[pid]/statm
>
> --
> Jan Chaloupka
> ------------------------------
> * Software Engineer *
> * ENG Base Operating Systems *
> * Red Hat Czech, s. r. o. *
> * UTC+1 (CET), jchaloup *
>
>
--
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
prev parent reply other threads:[~2014-07-10 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 9:10 [PATCH] proc.5: Add missing fields to /proc/PID/stat Mijo Safradin
[not found] ` <1404983420-21338-1-git-send-email-mijo-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2014-07-10 9:34 ` Jan Chaloupka
[not found] ` <53BE5E17.8050509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2014-07-10 10:21 ` Michael Kerrisk (man-pages)
2014-07-10 10:24 ` Mijo Safradin [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=alpine.DEB.2.02.1407101216210.30830@tp530.de.ibm.com \
--to=safradin-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=jchaloup-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-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