From: Bernd Petrovitsch <bernd@firmix.at>
To: "Mattias Engdegård" <mattias@virtutech.se>
Cc: Valdis.Kletnieks@vt.edu, cfriesen@nortel.com,
linux-kernel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: Add pselect, ppoll system calls.
Date: Tue, 14 Jun 2005 16:54:53 +0200 [thread overview]
Message-ID: <1118760893.11557.94.camel@tara.firmix.at> (raw)
In-Reply-To: <200506141442.j5EEgKJ11377@virtutech.se>
Trimmed Cc: so reduce mail on already mail-overloaded folks.
On Tue, 2005-06-14 at 16:42 +0200, =?ISO-8859-1?Q?Mattias Engdeg=E5rd?=
wrote:
> >> I don't have the POSIX specs handy, but I see no reason we could not let
> >> it use a warpless monotonic clock.
> >
> >You have already one - the uptime of the system.
>
> For example, yes.
>
> >Doing "Relative timeouts" with "gettimeofday()" is a strategic error.
> >Specify the timeout und use (the return value of) times(2) for this.
>
> Having an interface use absolute timeouts will avoid this strategic error,
If the absolute timeouts means "the uptime in some point in the future",
yes.
If the absolute timeouts means "the time in the real world", then it
*is* the strategic error. This "time in the real world" (if it is usable
on the user interface), is neither monotonic nor warpless.
> simplify common code, and reduce the number of needed syscalls.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2005-06-14 15:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 19:38 Mattias Engdegård
2005-06-13 19:57 ` Chris Friesen
2005-06-13 20:08 ` Mattias Engdegård
2005-06-13 20:23 ` Valdis.Kletnieks
2005-06-14 14:07 ` Mattias Engdegård
2005-06-14 14:16 ` Bernd Petrovitsch
2005-06-14 14:42 ` Mattias Engdegård
2005-06-14 14:54 ` Bernd Petrovitsch [this message]
2005-06-14 15:27 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2005-06-10 22:58 David Woodhouse
2005-06-12 22:48 ` Alan Cox
2005-06-13 0:26 ` Linus Torvalds
2005-06-13 1:16 ` jnf
2005-06-13 3:26 ` Linus Torvalds
2005-06-13 6:22 ` Ulrich Drepper
2005-06-13 9:16 ` bert hubert
2005-06-13 9:41 ` David Woodhouse
2005-06-13 11:05 ` Christoph Hellwig
2005-06-13 11:14 ` Jakub Jelinek
2005-06-13 11:24 ` David Woodhouse
2005-06-13 15:38 ` Ulrich Drepper
2005-06-13 16:02 ` David Woodhouse
2005-06-13 16:10 ` Ulrich Drepper
2005-06-13 16:29 ` David Woodhouse
2005-06-13 16:31 ` Ulrich Drepper
2005-06-13 21:58 ` David Woodhouse
2005-06-13 22:01 ` Ulrich Drepper
2005-06-13 16:36 ` Jakub Jelinek
2005-06-15 11:36 ` David Woodhouse
2005-08-05 11:58 ` Michael Kerrisk
2005-08-05 12:49 ` Michael Kerrisk
2005-08-25 0:04 ` David Woodhouse
2005-08-25 0:34 ` Ulrich Drepper
2005-08-26 6:46 ` Michael Kerrisk
2005-06-13 15:35 ` Ulrich Drepper
2005-06-13 7:23 ` Benjamin Herrenschmidt
2005-06-13 7:29 ` David Woodhouse
2005-06-13 22:56 ` Benjamin Herrenschmidt
2005-06-13 11:15 ` Alan Cox
2005-06-13 11:27 ` David Woodhouse
2005-06-13 15:40 ` Ulrich Drepper
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=1118760893.11557.94.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cfriesen@nortel.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattias@virtutech.se \
/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
all inboxes | Powered by JetHome®