From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] time
Date: Mon, 13 Aug 2018 09:45:25 +0200 [thread overview]
Message-ID: <A6F23995C22748448AC4D80E9037C5CE@felloff.net> (raw)
In-Reply-To: 6c11e603325ca644a5068fd3d0f30df1@rebk.znet
>> internally, user/kernel time accounting works by hzclock()
>> just incrementing a per process counter of ticks. which is
>> not very precise and processes can evade time being accounted
>> by yielding so they'd miss the timer interrupt.
>
> Are there any other reasons for the real time count to become erratic
> or inconsistent?
the realtime count is about the easist to get right. thats done by
just recording start time on fork and then take the difference on
exit.
> How does this work on a multi-core machine?
the same as on a single core.
--
cinap
next reply other threads:[~2018-08-13 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 7:45 cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-12 21:07 cinap_lenrek
2018-08-12 22:28 ` BurnZeZ
2018-08-12 19:11 cinap_lenrek
2018-08-12 20:49 ` BurnZeZ
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=A6F23995C22748448AC4D80E9037C5CE@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).