From: Robert Love <rml@tech9.net>
To: mark manning <mark.manning@fastermail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: nanosleep
Date: 10 Apr 2002 02:01:35 -0400 [thread overview]
Message-ID: <1018418496.903.228.camel@phantasy> (raw)
In-Reply-To: <20020410055708.9474.qmail@fastermail.com>
On Wed, 2002-04-10 at 01:57, mark manning wrote:
> hrm - im confiused now - how can you do a n NANO second delay when the
> resolution is 10 mili seconds ?
Uh, you can't - that was his point.
You can try, and you will certainly sleep at least that long, but any
time given modulo 10ms is out the door ...
Like I said, check out the high resolution timers project.
Robert Love
next prev parent reply other threads:[~2002-04-10 6:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 5:57 nanosleep mark manning
2002-04-10 6:01 ` Robert Love [this message]
2002-04-13 21:53 ` nanosleep andrew may
2002-04-14 20:37 ` nanosleep H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2002-04-10 4:42 nanosleep mark manning
2002-04-10 5:47 ` nanosleep H. Peter Anvin
2002-04-10 4:41 nanosleep mark manning
2002-04-10 5:57 ` nanosleep Robert Love
2002-04-10 3:22 nanosleep mark manning
2002-04-09 23:24 nanosleep mark manning
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=1018418496.903.228.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.manning@fastermail.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox