From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Michael Frank <mhf@linuxmail.org>,
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: Wed, 17 Mar 2004 09:28:32 +1300 [thread overview]
Message-ID: <1079468912.3400.96.camel@calvin.wpcb.org.au> (raw)
In-Reply-To: <20040316151003.GA24837@atrey.karlin.mff.cuni.cz>
Hi.
On Wed, 2004-03-17 at 04:10, Pavel Machek wrote:
> 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).
The NFS example was just one example; they are intended for 'suspend at
any load'. Actually, I should say, they're intended for 'suspend first
time at any load'. Maybe I should go back into the mailing list logs
from around the time when we made the change, to see again the kind of
issues we were attacking.
> 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.
I believe we achieve that. All the hooks do is atomically adjust a
counter of the number of busy processes, adjust process flags (in the
case of processes running sync), and check that we're not trying to
suspend. None of those things should affect reliability, and months of
testing by many users has not given any indication that they do.
> > 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.
Not arguing there. I either want to merge the whole lot at once
(unlikely, I know), or in discrete patches. I'm sure there must be some
bugs left somewhere that people will spot.
Nigel
--
Nigel Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6253 0250 (home)
Evolution (n): A hypothetical process whereby infinitely improbable events occur
with alarming frequency, order arises from chaos, and no one is given credit.
next prev parent reply other threads:[~2004-03-16 22:34 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
2004-03-16 20:28 ` Nigel Cunningham [this message]
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=1079468912.3400.96.camel@calvin.wpcb.org.au \
--to=ncunningham@users.sourceforge.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@ucw.cz \
--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®