lkml.org 
[lkml]   [2009]   [Aug]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] proc: let task status file print utime and stime.
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.


\
 
 \ /
  Last update: 2009-08-17 08:19    [W:0.033 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site