public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org, richard@hughsie.com
Subject: Re: suspend and hibernate nomenclature
Date: Sun, 21 May 2006 00:39:55 +0200	[thread overview]
Message-ID: <20060520223955.GB8490@elf.ucw.cz> (raw)
In-Reply-To: <200605201354.41229.david-b@pacbell.net>

[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]

Hi!

> > > Things that really *must* wake up periodically should be using some API that
> > > interacts with RTC alarms, and those RTC alarms should be acting as system
> > > wakeup events.
> > 
> > But that means completely rewriting userspace.
> 
> Completely?  No.  Hardly anything really _requires_ real-time wakeups.
> 
> In any case, I can't possibly believe it's news to you that userspace code
> which uses periodic polling is troublesome ... it wasn't news in the 1980s,
> or 1990s, so it can't be news now.  That's not just from the power management
> perspective; it also makes trouble in GUI applications architecture
> too.

Well, maybe it is not news to _me_, but it is certainly news to
application writers.

Battery applet requires polling -- we have no battery interface that
is event-driven, for example. Then you have clock on the desktop. Then
there's blinking cursor (in X) at HZ/5 or something like that.

How can kernel know which sleep is "important enough" to wake up
system for it?

Like, yes, we can probably do that on embedded platforms, but for
something running KDE/Gnome?

[Now, it is true that things are getting better. One of tricks is to
make sure all the periodic polling happens synchronized (=> cpu can
sleep for longer intervals between polls), and there are tricks like
"only blink X cursor 5 times", but... try running timertop on
KDE/Gnome system...] 

> > > There's also non-automated sleep too ... what "apmsleep" used to do when
> > > you told it to suspend until 7am (or for two hours, etc).  The same thing
> > > can be done with /sys/power/state and a wakeup-enabled RTC.
> > 
> > Yep, I should get it working one day.
> 
> See the attached.  "rtcwake -t $(( 5 * 60 * 60))" to sleep in standby mode
> for five hours, or until some other wakeup event kicks in.  :)

Thanks.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2006-05-20 22:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 18:02 suspend and hibernate nomenclature Richard Hughes
2006-05-08 15:05 ` Jordan Crouse
2006-05-08 16:09   ` Richard Hughes
2006-05-08 20:01 ` Pavel Machek
2006-05-14 15:32   ` Richard Hughes
2006-05-14 15:39     ` Pavel Machek
2006-05-14 21:17       ` Rafael J. Wysocki
2006-05-08 23:47 ` David Brownell
2006-05-09  7:38   ` Richard Hughes
2006-05-09 15:57     ` David Brownell
2006-05-16 20:40       ` Pavel Machek
2006-05-18 19:56         ` David Brownell
2006-05-18 20:50           ` Pavel Machek
2006-05-19  2:25             ` David Brownell
2006-05-20 17:20               ` Pavel Machek
2006-05-20 19:23                 ` Alan Stern
2006-05-20 20:47                   ` David Brownell
2006-05-20 20:55                     ` Pavel Machek
2006-05-21 15:35                       ` Alan Stern
2006-05-20 20:54                 ` David Brownell
2006-05-20 22:39                   ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-16 20:47 Scott E. Preece

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=20060520223955.GB8490@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=david-b@pacbell.net \
    --cc=linux-pm@lists.osdl.org \
    --cc=richard@hughsie.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