mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Michael Frank <mhf@linuxmail.org>
Cc: Nigel Cunningham <ncunningham@users.sourceforge.net>,
	Patrick Mochel <mochel@digitalimplant.org>,
	Andrew Morton <akpm@digeo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Suspend development list <swsusp-devel@lists.sourceforge.net>
Subject: Re: [Swsusp-devel] Re: The verdict on the future of suspending to disk?
Date: Tue, 16 Mar 2004 16:10:05 +0100	[thread overview]
Message-ID: <20040316151003.GA24837@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <opr4yiu1ar4evsfm@smtp.pacific.net.th>

Hi!

> Without reliability and being able to suspend at any load
> (when the batteries/UPS go flat)  software suspend is all
> but useless.  What for suspend if it does not resume and
> eats work left in RAM?

It should suspend at any load, but AFAICR those hooks are not for
that. They are neccessary for "crashed nfs server case", which kill
-SIGSTOP does not handle. (IMNSHO thats bug in -SIGSTOP and pretty
orthogonal to swsusp).

> Common users objectives for a software suspend mechanism are:
> 
> 1. To not impair system reliability. It must run without crash
>       and reboots between kernel upgrades.
>       100 cycles in 2 hours is a quickie
>       1000 cycles in a day are a short test
>       xxxx cycles in a month are a life test

There's even more important goal. I'd call it

O. Do not impair system reliablity *when swsusp is not in use*.
   Do not make further development of system harder by putting too
   much hooks into other code.

> 2. To handle any cpu and io load
> 	10+ concurrent unixbenchs, 4 concurrent dd loops, nfs and ssh
>       cross accesses, Load avg 20-40, cs of 100,000, 20MB io
>       sustained for days at a cycle a minute... No freezing failures
> 
> 3. To support the spectrum of user requirements wrt functionality
> 	for portable, desktop, and embedded apps
> 
> 4. To handle driver suspend and resume at any time. Apps should not
>       have to be terminated.
> 
> Swsusp2 meets 1. and 2. and many of 3. Swsusp2 is also modular and can be
> expanded to add things like NFS suspend/resume.
> 
> 1. and 2. require a sophisticated freezing mechanism and kernel level
> "intrusion". Most of this "intrusion" is simetrical and easily understood.
> This is what UGLY macros are for.

I still do not believe 1. and 2. *require* that ugly hooks (as long as
your NFS server is up).

Now, what if NFS server is down? I'd not handle it for now; if your
harddrive stops working you can't suspend, too, and NFS is too similar
to disk.

> 3. Can be argued about: Compression or no compression, reboot functionality
>    for multi boot or not, Escape or no Escape (I need it every day) -
>    If you ever would dare to suspend you would want an Escape function too! 
>    :-)

For first merge, I'd like to have simplest possible version, that's no
compression, powerdown at the end, no escape.

> 4. Requires PM fixes and driver level intrusion, can be worked around by
>    killing apps and unloading drivers. Eventually this has to be fixed.

Yes. People are working on that.
									Pavel
-- 
Horseback riding is like software...
...vgf orggre jura vgf serr.

  reply	other threads:[~2004-03-16 15:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16  3:38 Nigel Cunningham
2004-03-16  8:05 ` [Swsusp-devel] " Karol Kozimor
2004-03-16 11:37 ` Pavel Machek
2004-03-16 12:15   ` Pavel Machek
2004-03-16 13:38     ` [Swsusp-devel] " Michael Frank
2004-03-16 15:10       ` Pavel Machek [this message]
2004-03-16 20:28         ` Nigel Cunningham
2004-03-16 20:13   ` Nigel Cunningham

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=20040316151003.GA24837@atrey.karlin.mff.cuni.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhf@linuxmail.org \
    --cc=mochel@digitalimplant.org \
    --cc=ncunningham@users.sourceforge.net \
    --cc=swsusp-devel@lists.sourceforge.net \
    /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®