From: Davidlohr Bueso <dave.bueso@gmail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] [PATCH procfs] Add process age
Date: Mon, 26 Jul 2010 09:57:48 -0400 [thread overview]
Message-ID: <1280152668.2212.1.camel@cowboy> (raw)
In-Reply-To: <87fwz6it0e.fsf@basil.nowhere.org>
On Mon, 2010-07-26 at 09:47 +0200, Andi Kleen wrote:
> Davidlohr Bueso <dave.bueso@gmail.com> writes:
>
> > On Fri, 2010-07-23 at 21:35 +0300, Alexey Dobriyan wrote:
> >> On Fri, Jul 23, 2010 at 01:47:51PM -0400, Davidlohr Bueso wrote:
> >> > This patch exports a process's age, in seconds, adding a /proc/#/age file.
> >>
> >> What for?
> >
> > I have not found any straight way to get the run time of a processes,
> > without having to interpret the start_time entry in /proc/#/stat and
> > manually subtract the uptime from it.
>
> That sounds like something an user space program should simply do.
> Perhaps you can add it as a new optional "-o" field in "ps" ?
>
True, but there are also many other no-so-useful files under /proc that
can also be replaced by userspace apps.
Davidlohr
next prev parent reply other threads:[~2010-07-26 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 17:47 [RFC] [PATCH procfs] Add process age Davidlohr Bueso
2010-07-23 18:35 ` Alexey Dobriyan
2010-07-23 18:47 ` Davidlohr Bueso
2010-07-23 23:16 ` Sergey V.
2010-07-26 7:47 ` Andi Kleen
2010-07-26 13:57 ` Davidlohr Bueso [this message]
2010-07-26 14:48 ` Andi Kleen
2010-07-26 15:10 ` Davidlohr Bueso
2010-07-28 6:56 ` Américo Wang
2010-07-30 14:58 ` Davidlohr Bueso
2010-07-30 14:58 ` Davidlohr Bueso
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=1280152668.2212.1.camel@cowboy \
--to=dave.bueso@gmail.com \
--cc=adobriyan@gmail.com \
--cc=andi@firstfloor.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.