From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: RUSAGE_THREAD
Date: Tue, 28 Jun 2016 19:47:00 +0200 [thread overview]
Message-ID: <20160628174700.GB19691@port70.net> (raw)
In-Reply-To: <CACCP0GqX3nzAeZ33fCfNDx44kpHLYqUWtxkH2oAgHN3HQGXpcw@mail.gmail.com>
* Raphael Cohn <raphael.cohn@stormmq.com> [2016-06-28 17:58:22 +0100]:
> On 28 June 2016 at 17:52, Rich Felker <dalias@libc.org> wrote:
> > On Tue, Jun 28, 2016 at 04:00:45PM +0100, Raphael Cohn wrote:
> > > Hi,
> > >
> > > I'm in the process of compiling ZFS on Linux against musl. ZFS seems to
> > > make a few slightly glibc-like assumptions, one of which is the use of
> > > RUSAGE_THREAD. Musl seems to lack a definition of this in sys/resource.h.
> > > Is this deliberate?
> > >
> > > Glibc defines RUSAGE_THREAD as 1, but musl already uses this value for
> > > RUSAGE_CHILDREN (glibc sets this as -1). What would be the correct value
> > > for RUSAGE_THREAD with musl?
> >
> > Maybe this is incorrect in musl then. Can anyone confirm? The values
> > are determined by (i.e. have to match) the kernel.
> >
> > Rich
> >
>
> I've grabbed the 4.6 linux kernel sources. A quick grep suggests
> include/uapi/linux/resource.h defines it as 1. Additionally, in this file:-
>
> RUSAGE_SELF is 0 (I believe this is also the value musl uses).
> RUSAGE_CHILDREN is -1
> RUSAGE_BOTH is -2 (not in glibc; not mentioned in the getrusage man pages I
> have).
>
> What does anyone else think?
yes it seems the kernel definitions are
#define RUSAGE_SELF 0
#define RUSAGE_CHILDREN (-1)
#define RUSAGE_BOTH (-2) /* sys_wait4() uses this */
#define RUSAGE_THREAD 1 /* only the calling thread */
on all targets
_BOTH means _SELF+_CHILDREN and is used in the implementation of wait
in the kernel.
prev parent reply other threads:[~2016-06-28 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 15:00 RUSAGE_THREAD Raphael Cohn
2016-06-28 16:52 ` RUSAGE_THREAD Rich Felker
2016-06-28 16:58 ` RUSAGE_THREAD Raphael Cohn
2016-06-28 17:47 ` Szabolcs Nagy [this message]
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=20160628174700.GB19691@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).