[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070409181833.53eb2be9.akpm@linux-foundation.org>
Date: Mon, 9 Apr 2007 18:18:33 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: William Lee Irwin III <wli@...omorphy.com>
Cc: Eric Dumazet <dada1@...mosbay.com>, linux-kernel@...r.kernel.org
Subject: Re: per-thread rusage
On Mon, 9 Apr 2007 18:12:57 -0700
William Lee Irwin III <wli@...omorphy.com> wrote:
> On Mon, 9 Apr 2007 17:42:01 -0700 William Lee Irwin III <wli@...omorphy.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists