public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>, linux-kernel@vger.kernel.org
Subject: Re: per-thread rusage
Date: Mon, 9 Apr 2007 18:18:33 -0700	[thread overview]
Message-ID: <20070409181833.53eb2be9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070410011257.GC2986@holomorphy.com>

On Mon, 9 Apr 2007 18:12:57 -0700
William Lee Irwin III <wli@holomorphy.com> wrote:

> On Mon, 9 Apr 2007 17:42:01 -0700 William Lee Irwin III <wli@holomorphy.com> wrote:
> >>  My use for it is report generation in VM (and possibly other)
> >> testcases.
> 
> On Mon, Apr 09, 2007 at 05:53:52PM -0700, Andrew Morton wrote:
> > OK.  The cool kids are using taskstats for this sort of thing now, but I
> > note that taskstats is inexplicably missing the context-switch accounting,
> > and perhaps other things?
> 
> Sounds interesting. I'll poke around there for testcase affairs if I
> get moving on them first. I've no sentimental attachment to the rusage
> patch, so if taskstats do happen to displace this, I'm not concerned.
> (That said, it may still make sense to do this for the purposes of API
> compatibility. I'll keep it moving along until it's all decided.)
> 

rusage() is a bit easier to use, as it delivers synchronously at task exit.
 taskstats delivers over netlink into a separate process (and can be polled
at any time during task execution) but does require new skills, more
(Linux-specific) code and perhaps more complex synchronisation.


  reply	other threads:[~2007-04-10  1:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-04 17:29 per-thread rusage William Lee Irwin III
2007-04-04 17:48 ` Eric Dumazet
2007-04-04 18:10   ` William Lee Irwin III
2007-04-09 23:53     ` Andrew Morton
2007-04-10  0:42       ` William Lee Irwin III
2007-04-10  0:53         ` Andrew Morton
2007-04-10  1:12           ` William Lee Irwin III
2007-04-10  1:18             ` Andrew Morton [this message]
2007-05-01 17:29         ` Bill Irwin
2007-05-01 18:39           ` Ulrich Drepper
2007-05-01 20:24             ` Bill Irwin
2007-05-01 22:10               ` Ulrich Drepper
2007-05-01 22:27                 ` Theodore Tso
2007-05-01 22:34                   ` Bill Irwin
2007-05-01 23:04                     ` Alan Cox
2007-05-01 23:17                       ` Bill Irwin
2007-05-02  5:05                       ` Balbir Singh
2007-05-02  0:17                   ` Ulrich Drepper
2007-05-02  4:31                     ` Theodore Tso
2007-05-02  4:57                       ` Ulrich Drepper
2007-05-01 22:29                 ` Bill Irwin
2007-04-04 22:36 ` Valdis.Kletnieks
2007-04-05  4:09   ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2007-04-10 20:10 Oleg Nesterov

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=20070409181833.53eb2be9.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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