From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] sleep(2) historical question
Date: Wed, 28 Nov 2012 09:46:39 -0500 [thread overview]
Message-ID: <aa54345089bee0e0d22a2ba611475df5@brasstown.quanstro.net> (raw)
In-Reply-To: <CAOw7k5iz6BVZq-WDBJOruqex+GvzCBg6xWiELGkevKYeskY_cA@mail.gmail.com>
On Wed Nov 28 09:36:36 EST 2012, charles.forsyth@gmail.com wrote:
> Because they claim to be providing a service that's not actually being provided.
>
> On 28 November 2012 13:30, erik quanstrom <quanstro@quanstro.net> wrote:
> > why do extra zeros on the right bother you?
sleep(2) says.
DESCRIPTION
Sleep suspends the current process for the number of mil-
liseconds specified by the argument. The actual suspension
time may be a little more or less than the requested time.
from experience, i've found that stock 386 kernels on older hardware
yield a sleep resolution of 10ms or more.
so clearly the argument to sleep is not directly tied to the resolution of
the clock. and i think tying the two together would invent a
new requirement and assume too much on the hardware.
- erik
next prev parent reply other threads:[~2012-11-28 14:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 23:19 erik quanstrom
2012-11-28 7:37 ` Charles Forsyth
2012-11-28 12:57 ` erik quanstrom
2012-11-28 13:10 ` Charles Forsyth
2012-11-28 13:30 ` erik quanstrom
2012-11-28 14:35 ` Charles Forsyth
2012-11-28 14:46 ` erik quanstrom [this message]
2012-11-28 18:58 ` Bakul Shah
2012-11-28 19:10 ` Charles Forsyth
2012-11-28 19:28 ` erik quanstrom
2012-11-28 18:56 ` cinap_lenrek
2012-11-28 19:38 ` Bakul Shah
2012-11-28 20:58 ` Charles Forsyth
2012-11-28 21:02 ` erik quanstrom
2012-11-28 21:13 ` Charles Forsyth
2012-11-28 21:19 ` erik quanstrom
2012-11-28 21:21 ` erik quanstrom
2012-11-28 21:43 ` Bakul Shah
2012-11-29 0:12 ` Charles Forsyth
2012-11-29 8:12 ` arnold
2012-11-29 9:19 ` Charles Forsyth
2012-11-29 15:17 ` erik quanstrom
2012-11-28 19:27 ` David Arnold
2012-11-28 21:12 ` Charles Forsyth
2012-11-28 19:29 ` erik quanstrom
2012-11-28 19:54 ` Bakul Shah
2012-11-28 19:57 ` erik quanstrom
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=aa54345089bee0e0d22a2ba611475df5@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).