From: Bill Irwin <bill.irwin@oracle.com>
To: Ulrich Drepper <drepper@gmail.com>
Cc: Bill Irwin <bill.irwin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Eric Dumazet <dada1@cosmosbay.com>,
linux-kernel@vger.kernel.org, wli@holomorphy.com
Subject: Re: per-thread rusage
Date: Tue, 1 May 2007 13:24:56 -0700 [thread overview]
Message-ID: <20070501202456.GR26598@holomorphy.com> (raw)
In-Reply-To: <a36005b50705011139p361dbc46ube0da5e42955f8b0@mail.gmail.com>
On 5/1/07, Bill Irwin <bill.irwin@oracle.com> wrote:
>> 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,...),
On Tue, May 01, 2007 at 11:39:46AM -0700, Ulrich Drepper wrote:
> RUSAGE_LWP is a remnant of Solaris' M-on-N thread library days. No
> reason to got there. Use RUSAGE_THREAD. Even though the kernel calls
> the process and process group, at userland these are threads and
> processes.
Well, this is just the part where I'm surveying how other OS's report
getrusage-like info on a per-thread basis. As far as this is concerned,
RUSAGE_LWP is just Solaris nomenclature for it. The implementation
details (e.g. M:N thread disambiguation) are not so important for this.
What I think it means is "Solaris and AIX pass a nonstandard flag to
getrusage() for the same purpose."
And actually, you're a good person to ask about all this. How do other
kernels/OS's report per-thread analogues of rusage information? Googling
for getrusage() manpages is probably not going to find ones that, say,
force userspace to fish it out of /proc/ analogues and so on. The basic
idea is to try to do it similarly to how everyone else does so userspace
(I suppose this would include glibc) don't have to bend over backward to
accommodate it. Or basically to do what everyone expects.
- wli
next prev parent reply other threads:[~2007-05-01 20:25 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
2007-05-01 18:39 ` Ulrich Drepper
2007-05-01 20:24 ` Bill Irwin [this message]
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=20070501202456.GR26598@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=drepper@gmail.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