From: Nigel Cunningham <ncunningham@users.sourceforge.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>,
Michael Frank <mhf@linuxmail.org>
Subject: Re: Remove pmdisk from kernel
Date: Tue, 16 Mar 2004 09:14:19 +1300 [thread overview]
Message-ID: <1079381659.5356.73.camel@calvin.wpcb.org.au> (raw)
In-Reply-To: <20040315135328.0f704933.akpm@osdl.org>
Hi.
On Tue, 2004-03-16 at 10:53, Andrew Morton wrote:
> Nigel Cunningham <ncunningham@users.sourceforge.net> wrote:
> >
> > On Tue, 2004-03-16 at 10:21, Andrew Morton wrote:
> > > Pavel Machek <pavel@ucw.cz> wrote:
> > > >
> > > > I believe that you don't want swsusp2 in 2.6. It has hooks all over
> > > > the place:
> > > > ...
> > > > 109 files changed, 3254 insertions(+), 624 deletions(-)
> > >
> > > Ahem. Agreed.
> >
> > 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?
>
> It would make us happier. Even happier would be a series of small, well
> explained patches which bring swsusp into a final shape upon which more
> than one developer actually agrees.
I'd love to do that too. Unfortunately I'm really busy with my new job,
so things have progressed far more slowly than I'd have liked. I'm also
not sure how to deal with some of the changes that just about completely
rewrite sections.
> These wholesale replacements and deletions are an indication that something
> has gone wrong with the development process here.
I spent a long time trying to get the freezer working reliably with the
kind of implementation Pavel uses. The problem I kept running into time
and again was that you can't know dependancies between processes when it
comes to signalling them; process A might happily be frozen, but then
process B can't be frozen becaue it is waiting on something process A
has (eg ls/nfsd). By tracking which processes are in those
'can't-be-frozen-here' sections, I have managed to make the freezer far
more reliable, even under high load. Michael Frank has done some extreme
stress testing and can verify this.
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-15 22:22 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 [this message]
2004-03-16 0:56 ` Pavel Machek
2004-03-15 23:27 ` Nigel Cunningham
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=1079381659.5356.73.camel@calvin.wpcb.org.au \
--to=ncunningham@users.sourceforge.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhf@linuxmail.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®