From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sleep(2) historical question
Date: Wed, 28 Nov 2012 21:12:53 +0000 [thread overview]
Message-ID: <CAOw7k5hRmDTUvRqYbZisgJrs8WADKHgpkjZssr3S6Ws=k_+zCw@mail.gmail.com> (raw)
In-Reply-To: <46481E9E-F3CD-4F75-8B2A-405829DFD5D2@pobox.com>
If you look at the manual pages for nanosleep, clock_nanosleep and
others on Linux you'll see that they have many bits
of advice, BUGS notes, and other statements to the effect that the
standard things do not work well, and most need some
sort of real-time support to do anything sensible. An earlier variant
did a busy wait when needed (which is unsurprising,
but assumes processor wiring, and no scheduling away from the process).
On 28 November 2012 19:27, David Arnold <davida@pobox.com> wrote:
> Is POSIX' nanosleep() or old-POSIX/BSD/XOpen's usleep() out of the question?
next prev parent reply other threads:[~2012-11-28 21:12 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
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 [this message]
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='CAOw7k5hRmDTUvRqYbZisgJrs8WADKHgpkjZssr3S6Ws=k_+zCw@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--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).