From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Nigel Cunningham <ncunningham@linuxmail.org>,
Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] Freeze bdevs when freezing processes.
Date: Tue, 24 Oct 2006 00:15:17 +1000 [thread overview]
Message-ID: <453CCE75.20302@yahoo.com.au> (raw)
In-Reply-To: <200610231607.17525.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> This case is a bit special. I don't think it would be right to require every
> device driver writer to avoid modifying RCU pages from the interrupt
> context, because that would break the suspend to disk ...
>
> Besides, if there is an RCU page that we _know_ we can use to store the image
> in it, we can just include this page in the image without copying. This
> already gives us one extra free page for the rest of the image and we can
> _avoid_ creating two images which suspend2 does and which adds a _lot_ of
> complexity to the code.
If you don't mind me asking... what are these RCU pages you speak of?
I couldn't work it out by grepping kernel/power/*
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-10-23 14:15 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 4:12 [PATCH] Freeze bdevs when freezing processes Nigel Cunningham
2006-10-23 10:36 ` Rafael J. Wysocki
2006-10-23 12:09 ` Nigel Cunningham
2006-10-23 14:07 ` Rafael J. Wysocki
2006-10-23 14:15 ` Nick Piggin [this message]
2006-10-23 14:20 ` Rafael J. Wysocki
2006-10-23 23:05 ` Nigel Cunningham
2006-10-23 16:55 ` Andrew Morton
2006-10-23 17:14 ` Pavel Machek
2006-10-23 17:50 ` Andrew Morton
2006-10-23 18:06 ` Pavel Machek
2006-10-23 19:19 ` Rafael J. Wysocki
2006-10-23 22:52 ` Nigel Cunningham
2006-10-24 7:57 ` Rafael J. Wysocki
2006-10-24 8:21 ` Nigel Cunningham
2006-10-23 21:39 ` Matthew Garrett
2006-10-23 22:12 ` Rafael J. Wysocki
2006-10-24 7:58 ` Pavel Machek
2006-10-23 22:58 ` Nigel Cunningham
2006-10-24 8:01 ` Pavel Machek
2006-10-23 23:22 ` Nigel Cunningham
2006-10-24 8:37 ` Rafael J. Wysocki
2006-10-24 14:44 ` David Chinner
2006-10-24 15:29 ` Rafael J. Wysocki
2006-10-24 16:20 ` Oleg Verych
2006-10-24 16:27 ` Oleg Verych
2006-10-24 17:08 ` Christoph Hellwig
2006-10-25 8:05 ` Pavel Machek
2006-10-24 16:33 ` David Chinner
2006-10-24 21:37 ` Pavel Machek
2006-10-25 0:13 ` David Chinner
2006-10-25 8:10 ` Pavel Machek
2006-10-25 8:38 ` David Chinner
2006-10-25 8:47 ` Pavel Machek
2006-10-25 12:32 ` Rafael J. Wysocki
2006-10-25 13:23 ` Nigel Cunningham
2006-10-25 19:05 ` Rafael J. Wysocki
2006-10-26 7:30 ` David Chinner
2006-10-26 8:18 ` Nigel Cunningham
2006-10-26 8:48 ` Rafael J. Wysocki
2006-10-26 8:57 ` David Chinner
2006-10-26 9:11 ` Rafael J. Wysocki
2006-10-27 1:38 ` David Chinner
2006-10-27 14:37 ` Rafael J. Wysocki
2006-10-29 17:35 ` Pavel Machek
2006-10-29 23:29 ` Rafael J. Wysocki
2006-10-29 23:46 ` Nigel Cunningham
2006-10-26 9:18 ` Nigel Cunningham
2006-10-26 9:08 ` Rafael J. Wysocki
2006-10-25 8:12 ` Rafael J. Wysocki
2006-10-24 17:06 ` Christoph Hellwig
2006-10-24 19:09 ` Rafael J. Wysocki
2006-10-24 21:26 ` Pavel Machek
2006-10-24 21:33 ` Christoph Hellwig
2006-10-24 21:43 ` Pavel Machek
2006-10-24 22:19 ` Nigel Cunningham
2006-10-24 20:16 ` Rafael J. Wysocki
2006-10-24 22:17 ` Nigel Cunningham
2006-10-24 20:38 ` Christoph Hellwig
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=453CCE75.20302@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.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.