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: Sat, 20 May 2006 19:20:51 +0200 [thread overview]
Message-ID: <20060520172051.GL2946@elf.ucw.cz> (raw)
In-Reply-To: <200605181925.30967.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]
On Čt 18-05-06 19:25:29, David Brownell wrote:
> On Thursday 18 May 2006 1:50 pm, Pavel Machek wrote:
>
> > Well, will it ever go to sleep? In such case? There are many things
> > that wake up periodically.
>
> Applications that constantly wake/poll are death to power management anyway,
> that's not news ... most of the "work" done by polling is wasted. When they
> get switched to no-timeout/blocking APIs, then they can sleep painlessly
> until a relevant wakeup event triggers.
Well, that is not how X app currently work :-(.
> 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.
> 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.
> > > As for downloading, that's why ethernet adapters have wake-on-lan (WOL)
> > > mechanisms. Likewise for other wakeup-capable devices, like a keyboard
> > > or mouse. Or even 3D engines, DSPs, SPUs, ...
> >
> > ?? WOL is for different functionality, I'm afraid. Or do you know
> > ethernet hub that automagically wakes machines when data come?
>
> No, that's exactly what WOL is designed for. A typical scenarios has
> the adapter waking up when the incoming packet is unicast to the MAC
> address of that host. The hub/switch would act normally.
I do not think WOL wakes that way. IIRC it needs magic ethernet
packet.
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 --]
next prev parent reply other threads:[~2006-05-20 17:20 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 [this message]
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
-- 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=20060520172051.GL2946@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