mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: Remove pmdisk from kernel
Date: Tue, 16 Mar 2004 12:27:36 +1300	[thread overview]
Message-ID: <1079393256.2043.5.camel@calvin.wpcb.org.au> (raw)
In-Reply-To: <20040316005618.GB1883@elf.ucw.cz>

Hi.

On Tue, 2004-03-16 at 13:56, Pavel Machek wrote:
> Hi!
> 
> > Most of those changes are hooks to make the freezer for more reliable.
> > That part of the functionality could be isolated from the bulk of
> > suspend2. Would that make you happy?
> 
> Yes, that would be very good. It would make it easy to see actual
> changes..
> 
> [I still do not understand why those hooks are neccessary... kill
> -SIGSTOP works, right?]

Not always. Take for example the case where you have an NFS mount and
happen to be doing an ls when the suspend cycle is started. If you
signal the NFSd threads before the ls thread, the NFS threads will
refrigerate okay, but the ls thread will fail to stop because it's
waiting for data from the nfsd threads.

The best way to test the reliability of the current freezer
implementation is to grab Michael's test patches. They can load the
system down with NFS access, kernel compiles, benchmarks and so on.
You'll quickly see the freezer fail. My implementation handles those
loads flawlessly, and where problems are found, they're easily fixed.

Regards,

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.


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 19:54 Pavel Machek
2004-03-15 20:53 ` Andrew Morton
2004-03-15 20:57   ` Pavel Machek
2004-03-15 21:21     ` Andrew Morton
2004-03-15 19:38       ` Nigel Cunningham
2004-03-15 21:53         ` Andrew Morton
2004-03-15 20:14           ` Nigel Cunningham
2004-03-16  0:56         ` Pavel Machek
2004-03-15 23:27           ` Nigel Cunningham [this message]
2004-03-16 10:17             ` Pavel Machek
2004-03-16 19:37               ` Nigel Cunningham
2004-03-16  1:32     ` Fedor Karpelevitch
     [not found]     ` <20040316091648.GB6301@pern.dea.icai.upco.es>
2004-03-16 10:11       ` Pavel Machek
2004-03-18  8:00       ` Romano Giannetti

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=1079393256.2043.5.camel@calvin.wpcb.org.au \
    --to=ncunningham@users.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@ucw.cz \
    /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®