mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mattias Engdegård" <mattias@virtutech.se>
To: Valdis.Kletnieks@vt.edu
Cc: cfriesen@nortel.com, jakub@redhat.com, torvalds@osdl.org,
	linux-kernel@vger.kernel.org, akpm@osdl.org, dwmw2@infradead.org,
	drepper@redhat.com
Subject: Re: Add pselect, ppoll system calls.
Date: Tue, 14 Jun 2005 16:07:54 +0200	[thread overview]
Message-ID: <200506141407.j5EE7sZ11314@virtutech.se> (raw)
In-Reply-To: <200506132023.j5DKNhoG021339@turing-police.cc.vt.edu> (Valdis.Kletnieks@vt.edu)

>Monotonic clocks are guaranteed to not go backward. A sudden warp 35
>seconds into the future when you have timers set for 15 and 20
>seconds into the future is still ugly....

I don't have the POSIX specs handy, but I see no reason we could not let
it use a warpless monotonic clock.

The problem of timeouts going wild when time is being warped applies
to syscalls using relative timeouts as well. Even when a relative
timeout is wanted, it is usually transformed (via gettimeofday or
similar) to an absolute timeout:

   T = some_clock() + dT
   timeout = dT
   loop:
      poll(..., timeout)
      if (poll did not time out):
          now = some_clock()
          timeout = MAX(0, T - now)
          goto loop

This kind of code is very common, because the timeout is usually the
time to some event in the future. If some_clock() is subject to
warping (which is the case when gettimeofday() is used), then you have
the problem again.

  reply	other threads:[~2005-06-14 14:08 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 [this message]
2005-06-14 14:16         ` Bernd Petrovitsch
2005-06-14 14:42           ` Mattias Engdegård
2005-06-14 14:54             ` Bernd Petrovitsch
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=200506141407.j5EE7sZ11314@virtutech.se \
    --to=mattias@virtutech.se \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@osdl.org \
    --cc=cfriesen@nortel.com \
    --cc=drepper@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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®