From: "Peter T. Breuer" <ptb@inv.it.uc3m.es>
To: "Eric Piel" <Eric.Piel@tremplin-utc.net>
Cc: "Peter T. Breuer" <ptb@inv.it.uc3m.es>,
"john stultz" <johnstul@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: uptime increases during suspend
Date: Tue, 28 Mar 2006 05:57:11 +0200 (MET DST) [thread overview]
Message-ID: <200603280357.k2S3vBk14437@inv.it.uc3m.es> (raw)
In-Reply-To: <44286783.9000709@tremplin-utc.net> from "Eric Piel" at "Mar 28, 2006 00:30:27 am"
"Also sprach Eric Piel:"
> monotonic clock. Linux has such thing since few releases. Using
> CLOCK_MONOTONIC (cf "man 3 clock_gettime") may look much less hacky than
> using the uptime ;-)
Actually, the man page does not say anything about the behavior across
suspends, and ...
CLOCK_REALTIME
System-wide realtime clock. Setting this clock requires appro-
priate privileges.
CLOCK_MONOTONIC
Clock that cannot be set and represents monotonic time since
some unspecified starting point.
I'd understand both those wordings the same way! Well, I suppose
"cannot be set" means that at least humans can't willingly interfere with
it, but maybe something else can.
> Now... concerning the suspend effect on this clock, I don't know. It's
> probably the same problem as uptime: no official semantic has ever been
> stated yet... Does anyone know?
"Monotonic" means "always goes in the same direction", not "never
skips".
Peter
next prev parent reply other threads:[~2006-03-28 3:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 15:02 Jonathan Black
2006-03-25 15:10 ` Rafael J. Wysocki
2006-03-25 15:18 ` Jonathan Black
2006-03-26 21:38 ` Rafael J. Wysocki
2006-03-27 18:40 ` john stultz
2006-03-27 19:53 ` Peter T. Breuer
2006-03-27 20:01 ` linux-os (Dick Johnson)
2006-03-27 22:30 ` Eric Piel
2006-03-28 3:57 ` Peter T. Breuer [this message]
2006-03-27 21:37 ` Tomasz Torcz
2006-03-27 22:43 ` Rafael J. Wysocki
2006-03-29 14:52 ` Jonathan Black
2006-03-28 2:01 Peter T. Breuer
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=200603280357.k2S3vBk14437@inv.it.uc3m.es \
--to=ptb@inv.it.uc3m.es \
--cc=Eric.Piel@tremplin-utc.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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®