From: Bill Irwin <bill.irwin@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Eric Dumazet <dada1@cosmosbay.com>, linux-kernel@vger.kernel.org
Subject: Re: per-thread rusage
Date: Tue, 1 May 2007 10:29:37 -0700 [thread overview]
Message-ID: <20070501172937.GQ26598@holomorphy.com> (raw)
In-Reply-To: <20070410004201.GA2986@holomorphy.com>
On Mon, Apr 09, 2007 at 04:53:15PM -0700, Andrew Morton wrote:
>> Seems sane. Could we please get it tested and get a full description in
>> place? Something which provides enough detail for the manpage maintainers.
>> Also, a quick comparison between Linux's RUSAGE_THREAD and $other-os's
>> implementations would reduce the possibility of silly, cast-in-stone
>> incompatabilities.
On Mon, Apr 09, 2007 at 05:42:01PM -0700, William Lee Irwin III wrote:
> The latter is the more serious of the two. I'll go about investigating
> that as the primary task here. Testing and a more verbose patch
> description are clearly very little work.
> General maintenance-relevant commentary: This patch arose from an
> observation of a lacuna in the API. There are no bugs or apps broken
> awaiting this as a fix, so it's not needed by 2.6.22 or otherwise
> urgently. My use for it is report generation in VM (and possibly other)
> testcases. The ack-in-concept is good enough for me to go about
> sweeping up the OS/standards compatibility, testing, and documentation
> issues in the near future prior to resubmission.
A sort of note for me to refer back to when I get the rest of the way
here. AIX does this with getrusage(RUSAGE_THREAD,...), Solaris with
getrusage(RUSAGE_LWP,...), Tru64 and HP-UX seem to lack any obvious
way to do this at all, likewise for MacOS X and the opensource BSD's.
-- wli
next prev parent reply other threads:[~2007-05-01 17:30 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
2007-05-01 17:29 ` Bill Irwin [this message]
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=20070501172937.GQ26598@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.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.