From: Amerigo Wang <xiyou.wangcong@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Amerigo Wang <xiyou.wangcong@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Tatsuhiro Aoshima <tatsu.pc@gmail.com>,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH] proc: let task status file print utime and stime.
Date: Mon, 17 Aug 2009 14:18:21 +0800 [thread overview]
Message-ID: <20090817061821.GM5039@cr0.nay.redhat.com> (raw)
In-Reply-To: <20090817114242.1419bd1f.kamezawa.hiroyu@jp.fujitsu.com>
On Mon, Aug 17, 2009 at 11:42:42AM +0900, KAMEZAWA Hiroyuki wrote:
>On Mon, 17 Aug 2009 10:38:02 +0800
>Amerigo Wang <xiyou.wangcong@gmail.com> wrote:
>
>> On Sat, Aug 15, 2009 at 11:36:41PM +0900, KOSAKI Motohiro wrote:
>> >From: Tatsuhiro Aoshima <tatsu.pc@gmail.com>
>> >Subject: [PATCH] proc: let task status file print utime and stime.
>> >
>> >The task status file in proc file system did not contain
>> >user-time and system-time. Thus, users could not get
>> >those information of running task easily. I think
>> >these values should be provived in human readable format.
>> >By this patch, users can get stime and utime very easily.
>>
>>
>> Why? /proc/<pid>/stat already has these.
>>
>
>I wonder /proc/<pid>/stat is unreadable for usual human.
>Most of ents in /proc/<pid>/status is duplicated output of
>some other files(i.e. /proc/<pid>/stat) and /proc/<pid>/status is
>for human readble format.
Ah... in fact, I expected 'ps' can report this, however, surprisingly
it doesn't have this, at least not what I expect (unless I miss
something obvious).
>
>In another thinking, in old days, /proc/<pid>/stat was enough because most of
>users uses scanf() or some C langage to read fixed-format data.
>/proc/<pid>/status is useful for some script languages which has
>good parser per line.
>
Well... I think this work should be left to 'ps', e.g.
ps -o pid,utime,stime
'ps' is responsible to read /proc/<pid>/stat for the user.
Thanks.
next prev parent reply other threads:[~2009-08-17 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 14:36 KOSAKI Motohiro
2009-08-17 2:38 ` Amerigo Wang
2009-08-17 2:42 ` KAMEZAWA Hiroyuki
2009-08-17 6:18 ` Amerigo Wang [this message]
2009-08-17 6:22 ` KAMEZAWA Hiroyuki
2009-08-17 6:32 ` Amerigo Wang
2009-08-17 6:32 ` KAMEZAWA Hiroyuki
2009-08-17 8:34 ` Amerigo Wang
2009-08-18 16:27 ` KOSAKI Motohiro
2009-08-29 7:20 Tatsuhiro Aoshima
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=20090817061821.GM5039@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tatsu.pc@gmail.com \
--cc=yoshfuji@linux-ipv6.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
all inboxes | Powered by JetHome®