Re: Back to the future.

On Sat, 28 Apr 2007, Oliver Neukum wrote:

Am Samstag, 28. April 2007 01:50 schrieb David Lang:
3. make mounted filesystems read-only (possibly with snapshot/checkpoint)
4. unpause
5. save image (with full userspace available, including network)
6. shutdown system (throw away all userspace memory, no need to do graceful
    shutdown or nice kill signals, revert filesystem to snapshot/checkpoint if
    needed)

And then you'll have people wonder why the server which sent out all
those files has no log entries. You'd have to selectively unfreeze user
space, which is a cure worse than the desease.

Simply throwing away user space work is a bug. And no, you cannot say that
it'll be redone away, as you are throwing away accepted input, too.

when you are doing a suspend-to-disk I disagree with you. whoever is doing the suspend knows what is going on, and they can decide what needs to be done.

the only case where you have 'unexpected' work being thrown away is if you are suspending a network server, and the process of suspending it is going to cut all the network connections anyway so it's not a seamless process. In this case it's fair to let the sysadmin choose between loosing some logs or doing some other step to prevent this from happening (which could be to shutdown the network service, or load a iptables rule to block the service)

however, most of the uses of suspend-to-disk are going to be single-user machines and in that case telling the user that anything that they do after issuing the suspend is going to be lost is a perfectly sane thing to do.

and for that matter, if the snapshot is cheap enough, some people may choose to cron the snapshot portion of a suspend-to-disk evvery few min as a safety net for something going wrong. In this case they really do want all of userspace to keep working after the snapshot.

David Lang

Relevant Pages

  • Re: Attempted summary of suspend-blockers LKML thread
    ... typical situation is one where you're not attached to a wifi network. ... you count the kernel as that server), I'm saying that the decision that ... The disagreement is far more about the interface to userspace and userspace use of wakelocks. ... for example, if you want to abort the suspend because there is network activity, you can check the packet count of your network interface, decide to go to sleep, setup the network interface to raise a 'wake me up' interrupt, and then check to see if the packet count has changed. ...
    (Linux-Kernel)
  • Re: Device wont idle time out when my app is running
    ... Blackberry essentially requires you to use push e-mail. ... therefore allow network connections to be kept alive (or phone calls ... my code is woken up from suspend mode by timer interrupts or ... perform work similar to the power manager. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Device wont idle time out when my app is running
    ... therefore allow network connections to be kept alive (or phone calls ... my code is woken up from suspend mode by timer interrupts or ... perform work similar to the power manager. ...
    (microsoft.public.dotnet.framework.compactframework)
  • e100 kills S2R on my box, plus network drops dead
    ... ACPI handle has no context! ... during suspend / emergency-resume handling. ... thus it's not network-suitable after resume and hangs on some network APIs?) ...
    (Linux-Kernel)
  • Re: FC6 ipw3945 on Dell D820 not working. Whats the best way?
    ... For F7 to suspend, see http://people.freedesktop.org/~hughsient/quirk/ and do ... There seems to be several ways: the iwl* packages, the ipw* packages, ... This is an expensive laptop! ... If the network comes up and the ipw3945d is not ...
    (Fedora)