From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] Bug in time cmd?
Date: Wed, 11 Mar 2020 11:11:24 +1100 [thread overview]
Message-ID: <086912A0EAF35F67FD36D1DF0B200DD2@musolino.id.au> (raw)
In-Reply-To: 528d3ca3-2d46-77a8-a367-ffac684bd88c@qs.co.nz
These figures come from the Waitmsg structure returned by wait(2). The
'u' time is the total user time of the child process *and descendants*.
Given that you likely have a multiprocessor and mk will parallelise its
work according to the NPROC environemnt variable, that ought to explain
how you are able to achieve 14s of user time in only 6s real time.
next reply other threads:[~2020-03-11 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 0:11 Alex Musolino [this message]
2020-03-11 2:28 ` Trevor Higgins
2020-03-11 2:33 ` ori
2020-03-11 4:15 ` Trevor Higgins
2020-03-11 4:45 ` ori
-- strict thread matches above, loose matches on Subject: below --
2020-03-10 23:39 Trevor Higgins
2020-03-13 16:55 ` [9front] " Ethan Gardener
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=086912A0EAF35F67FD36D1DF0B200DD2@musolino.id.au \
--to=alex@musolino.id.au \
--cc=9front@9front.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 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).