From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@cyclades.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Freezer Patches.
Date: Thu, 2 Jun 2005 09:14:31 +0200 [thread overview]
Message-ID: <20050602071431.GA1841@elf.ucw.cz> (raw)
In-Reply-To: <1117676753.10888.105.camel@localhost>
Hi!
> > > > swsusp1 should not need any special casing of sync, right? We can
> > > > simply do sys_sync(), then freeze, or something like that. We could
> > > > even remove sys_sync() completely; it is not needed for correctness.
>
> Wrong. I guess you're only trying it on a machine that isn't actually
> doing anything :). I've forgotten whether it was this freezer
> implementation or the last, but we've been testing freezing processes
> when the load average exceeds 100. If you have a thread that is syncing
> and another that's submitting I/O continually (think dd, for example),
> you want this.
If sys_sync() is not working, *fix sys_sync()*. [BTW I see that
problem before and I think it is being worked on.] I'm *not* going to
work around it in refrigerator.
Pavel
next prev parent reply other threads:[~2005-06-02 7:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 12:33 Freezer Patches Nigel Cunningham
2005-06-01 13:02 ` Pavel Machek
2005-06-01 22:02 ` Benjamin Herrenschmidt
2005-06-01 22:13 ` Nigel Cunningham
2005-06-01 22:23 ` Benjamin Herrenschmidt
2005-06-01 22:08 ` Nigel Cunningham
2005-06-01 22:31 ` Pavel Machek
2005-06-01 22:45 ` Benjamin Herrenschmidt
2005-06-01 23:02 ` Pavel Machek
2005-06-02 0:35 ` Benjamin Herrenschmidt
2005-06-02 1:46 ` Nigel Cunningham
2005-06-02 1:49 ` Benjamin Herrenschmidt
2005-06-02 1:45 ` Nigel Cunningham
2005-06-02 1:48 ` Benjamin Herrenschmidt
2005-06-02 7:14 ` Pavel Machek [this message]
2005-06-02 7:26 ` Nigel Cunningham
2005-06-02 7:31 ` Pavel Machek
2005-06-02 7:36 ` Benjamin Herrenschmidt
2005-06-02 8:18 ` Nigel Cunningham
2005-06-02 21:47 ` Pavel Machek
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=20050602071431.GA1841@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
/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