From: David Schwartz <davids@webmaster.com>
To: <rusty@rustcorp.com.au>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 'select' failure or signal should not update timeout
Date: Sat, 27 Jul 2002 22:40:00 -0700 [thread overview]
Message-ID: <20020728054010.AAA25979@shell.webmaster.com@whenever> (raw)
In-Reply-To: <20020725163239.6c6e5ed6.rusty@rustcorp.com.au>
>NOT waittimeofday. You need a *new* measure which can't be set forwards
>or back if you want this to be sane. pthreads has absolute timeouts (eg.
>pthread_cond_timedwait), but they suck IRL for this reason.
>Rusty.
The usual way to deal with this is to have a 'clock watcher' thread. If the
system time jumps any significant amount, you signal all condition variables.
You're not guaranteed any particular latency anyway.
I don't think a DVD playback skipping when the system time is changed by a
large amount is unacceptable. However, the use of some sort of linear
timebase is much more convenient for many things.
DS
next prev parent reply other threads:[~2002-07-28 5:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200207171430.g6HEUvY23619@aztec.santafe.edu>
2002-07-19 9:52 ` [PATCH] 'select' failure or signal should not update timeout Paul Eggert
2002-07-20 0:38 ` Alan Cox
2002-07-20 5:57 ` Linus Torvalds
2002-07-21 15:36 ` Eric W. Biederman
2002-07-24 13:44 ` Jamie Lokier
2002-07-24 18:48 ` Linus Torvalds
2002-07-24 19:07 ` Chris Friesen
2002-07-24 23:30 ` Jamie Lokier
2002-07-25 6:32 ` Rusty Russell
2002-07-25 18:31 ` george anzinger
2002-07-28 5:40 ` David Schwartz [this message]
2002-07-25 16:35 ` Eric W. Biederman
2002-07-25 17:15 ` Jamie Lokier
2002-07-21 16:00 ` Christoph Rohland
2002-07-21 16:43 ` Linus Torvalds
2002-07-21 17:51 ` dean gaudet
2002-07-22 3:59 ` Edgar Toernig
2002-07-22 6:51 ` Christoph Rohland
2002-07-21 16:26 ` Ingo Molnar
2002-07-21 20:14 ` Richard Stallman
2002-07-20 3:59 dank
-- strict thread matches above, loose matches on Subject: below --
2002-07-21 3:34 Peter T. Breuer
2002-07-28 10:33 linux
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=20020728054010.AAA25979@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.