From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Oliver Neukum <oliver@neukum.org>, Pavel Machek <pavel@ucw.cz>,
Paul Mackerras <paulus@samba.org>,
Miklos Szeredi <miklos@szeredi.hu>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM
Date: Thu, 5 Jul 2007 08:48:15 +1000 [thread overview]
Message-ID: <200707050848.16163.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <200707041658.59588.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hi.
On Thursday 05 July 2007 00:58:58 Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> The syncing of filesystems from within the freezer in not needed for suspend
to
> RAM. Change freeze_processes() so that it doesn't execute sys_sync() and
> introduce the "syncing" version of it to be called from the hibernation code
> paths.
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
> ---
> include/linux/freezer.h | 14 ++++++++++++--
> kernel/power/disk.c | 2 +-
> kernel/power/main.c | 6 ++++++
> kernel/power/process.c | 8 +++++---
> kernel/power/user.c | 2 +-
> 5 files changed, 25 insertions(+), 7 deletions(-)
Looks ok, except that I wonder if you want the following fragment. It looks to
me (looking at rc6) like with this code, you'll currently call sys_sync twice
when suspending to ram. Maybe I'm misreading it. Also, shouldn't it be done
after taking the mutex?
Regards,
Nigel
> @@ -231,6 +232,11 @@ static int enter_state(suspend_state_t s
>
> if (!valid_state(state))
> return -ENODEV;
> +
> + printk("Syncing filesystems ... ");
> + sys_sync();
> + printk("done.\n");
> +
> if (!mutex_trylock(&pm_mutex))
> return -EBUSY;
>
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-04 22:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 14:58 [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM Rafael J. Wysocki
2007-07-04 22:48 ` Nigel Cunningham [this message]
2007-07-04 22:49 ` Pavel Machek
2007-07-04 22:49 ` Pavel Machek
2007-07-04 22:52 ` Nigel Cunningham
2007-07-05 11:28 ` Rafael J. Wysocki
2007-07-05 11:28 ` Rafael J. Wysocki
2007-07-05 11:37 ` Nigel Cunningham
2007-07-05 20:31 ` [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer Rafael J. Wysocki
2007-07-05 22:00 ` Pavel Machek
2007-07-05 22:00 ` Pavel Machek
2007-07-06 7:02 ` Rafael J. Wysocki
2007-07-06 7:02 ` Rafael J. Wysocki
2007-07-06 7:07 ` Nigel Cunningham
2007-07-06 7:07 ` Nigel Cunningham
2007-07-06 7:13 ` Miklos Szeredi
2007-07-06 7:13 ` Miklos Szeredi
2007-07-06 7:19 ` Nigel Cunningham
2007-07-06 7:36 ` Miklos Szeredi
2007-07-06 7:36 ` Miklos Szeredi
2007-07-07 11:48 ` possible solution for problem 2 (was Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer) Pavel Machek
2007-07-07 11:48 ` Pavel Machek
2007-07-06 7:19 ` [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer Nigel Cunningham
2007-07-06 8:59 ` Benjamin Herrenschmidt
2007-07-06 8:59 ` Benjamin Herrenschmidt
2007-07-06 9:05 ` Miklos Szeredi
2007-07-06 9:05 ` Miklos Szeredi
2007-07-06 9:13 ` Nigel Cunningham
2007-07-06 9:13 ` Nigel Cunningham
2007-07-06 9:31 ` Miklos Szeredi
2007-07-06 9:31 ` Miklos Szeredi
2007-07-06 10:00 ` Rafael J. Wysocki
2007-07-06 10:00 ` Rafael J. Wysocki
2007-07-05 11:37 ` [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM Nigel Cunningham
2007-07-04 22:52 ` Nigel Cunningham
2007-07-04 22:48 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2007-07-04 14:58 Rafael J. Wysocki
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=200707050848.16163.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=oliver@neukum.org \
--cc=paulus@samba.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.