From: Richard Coleman <coleman@math.gatech.edu>
To: rft@titus.cg.tuwien.ac.at
Cc: zsh-workers@math.gatech.edu
Subject: Re: time command bug in next headers?
Date: Tue, 03 Dec 1996 01:42:32 -0500 [thread overview]
Message-ID: <199612030642.BAA07569@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Mon, 02 Dec 1996 23:33:00 +0100." <9612022233.AA04440@raven.cg.tuwien.ac.at>
> Now. in a similar vein I have a few questions: there are a number of
> different system call interfaces for getting the user and system time of the
> process:
> times(...)
> vtimes(....)
> getrusage(...)
>
> What are the advantages and disadvantages of all these interfaces with respect
> to portability, overhead, and time resolution? On Nextstep at least it seems
> as if the getrusage(...) interface has a resolution of 1/100 of a second
> whereas times only has 1/60 sec resolution.
times() is part of the POSIX standard, and so should give the greatest
amount of portability for the future. At one time, the code used
getrusage() for BSD style machines, and times() for SYSV style machines.
The code to do this was very ugly (way too many #define's scattered in
the code). As part of the POSIX-ification of the code, this was all
rewritten to use times() everywhere.
The best way to fix the problem with the Next's is to just use
some #ifdef's to change the clock tick back to 1/60 (what in the
hell was Next thinking when they changed this).
rc
prev parent reply other threads:[~1996-12-03 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-02 22:33 Robert F Tobler
1996-12-03 6:42 ` Richard Coleman [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=199612030642.BAA07569@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--cc=rft@titus.cg.tuwien.ac.at \
--cc=zsh-workers@math.gatech.edu \
/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/zsh/
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).