From: Edgar Toernig <froese@gmx.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Christoph Rohland <cr@sap.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 'select' failure or signal should not update timeout
Date: Mon, 22 Jul 2002 05:59:48 +0200 [thread overview]
Message-ID: <3D3B8334.6755F14@gmx.de> (raw)
In-Reply-To: Pine.LNX.4.44.0207210934180.3794-100000@home.transmeta.com
Linus Torvalds wrote:
>
> In contrast, if you could just rely on absolute time in select(), you
> would be re-startable _and_ you'd not have to do the extra "what time is
> it now, so that I know what timeout I need to use for the next thing"?
I agree. Absolute times are nicer. Just one note: to make that work
you need a sane time source! gettimeofday jumps back and forth. You
want a getuptime (or similar) that gives a constant monotonous growing
value not adjustable from userspace (and preferably the same for all
processes).
Ciao, ET.
next prev parent reply other threads:[~2002-07-22 3:57 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
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 [this message]
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=3D3B8334.6755F14@gmx.de \
--to=froese@gmx.de \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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