From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jeremy Maitin-Shepard <jbms@cmu.edu>
Cc: Al Boldi <a1426z@gawab.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Hibernation Redesign
Date: Mon, 09 Jul 2007 14:45:35 +1000 [thread overview]
Message-ID: <4691BD6F.8000809@yahoo.com.au> (raw)
In-Reply-To: <87k5taw5vc.fsf@jbms.ath.cx>
Jeremy Maitin-Shepard wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> writes:
>>This is the Morton method, isn't it? :) I remember it sounding like a
>>very good idea when he brought it up, but I can't remember the details
>>of why it was rejected or what the problems were.
>
>
> Perhaps he did bring it up before I did. Please forward me a link to
> the thread or other reference if you can find it, as I'd be interested
> in reading it.
Sent in the next mail.
>>I suspect that freeing memory on the fly for the new kernel
>>would be non-trivial (but possible), however simply having a reserve
>>RAM region for the new kernel would be fine for a first step.
>
>
> Freeing memory on the fly should be extremely easy for the kernel (this
> is precisely what it does when it needs to satisfy an allocation). Note
> that the memory allocated need not be contiguous.
Yes, I have a rough idea about how page reclaim works. But I just
mean it would not be trivial to load the new kernel into physically
discontiguous memory. Possible of course, but I don't think kexec or
the setup code could quite cope ATM.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-07-09 4:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 14:37 Hibernation Redesign (was: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM) Al Boldi
2007-07-09 4:11 ` Hibernation Redesign Jeremy Maitin-Shepard
2007-07-09 4:29 ` Nick Piggin
2007-07-09 4:36 ` Jeremy Maitin-Shepard
2007-07-09 4:45 ` Nick Piggin [this message]
2007-07-09 4:54 ` Jeremy Maitin-Shepard
2007-07-09 4:58 ` Nick Piggin
2007-07-09 5:33 ` Nick Piggin
2007-07-09 6:22 ` Jeremy Fitzhardinge
2007-07-09 13:45 ` Pavel Machek
2007-07-09 14:02 ` Oliver Neukum
2007-07-09 14:26 ` Jeremy Maitin-Shepard
2007-07-09 15:09 ` Oliver Neukum
2007-07-09 15:27 ` Jeremy Maitin-Shepard
2007-07-09 4:39 ` Nick Piggin
2007-07-09 13:52 ` Pavel Machek
2007-07-09 15:30 ` Al Boldi
2007-07-10 1:29 ` Nick Piggin
2007-07-10 2:28 ` Jeremy Maitin-Shepard
2007-07-10 14:57 ` Jeremy Fitzhardinge
2007-07-10 17:25 ` Jeremy Maitin-Shepard
2007-07-10 22:59 ` Jeremy Fitzhardinge
2007-07-11 4:11 ` Al Boldi
2007-07-11 10:27 ` Rafael J. Wysocki
2007-07-11 10:42 ` Miklos Szeredi
2007-07-11 11:04 ` Rafael J. Wysocki
2007-07-11 11:11 ` Miklos Szeredi
2007-07-11 11:50 ` Rafael J. Wysocki
2007-07-11 11:54 ` Miklos Szeredi
2007-07-11 12:00 ` Nigel Cunningham
2007-07-11 12:09 ` Miklos Szeredi
2007-07-11 12:17 ` Nigel Cunningham
2007-07-11 12:27 ` Rafael J. Wysocki
2007-07-11 12:29 ` Miklos Szeredi
2007-07-11 21:04 ` Rafael J. Wysocki
2007-07-12 9:15 ` Pavel Machek
2007-07-12 22:13 ` Miklos Szeredi
2007-07-11 12:19 ` Rafael J. Wysocki
2007-07-11 12:49 ` Nigel Cunningham
2007-07-11 21:06 ` Rafael J. Wysocki
2007-07-11 12:11 ` Nigel Cunningham
2007-07-11 12:24 ` Miklos Szeredi
2007-07-11 12:46 ` Nigel Cunningham
2007-07-11 12:55 ` Miklos Szeredi
2007-07-11 13:16 ` Jeremy Maitin-Shepard
2007-07-11 20:48 ` Mark Lord
2007-07-11 21:14 ` Rafael J. Wysocki
2007-07-11 22:17 ` Al Boldi
2007-07-11 22:34 ` Rafael J. Wysocki
2007-07-11 23:12 ` Al Boldi
2007-07-11 23:31 ` Nigel Cunningham
2007-07-12 3:11 ` Al Boldi
2007-07-12 13:20 ` Rafael J. Wysocki
2007-07-16 6:04 ` Nick Piggin
2007-07-12 20:29 ` Jeremy Maitin-Shepard
2007-07-11 23:46 ` Nigel Cunningham
2007-07-11 17:55 ` david
2007-07-11 22:54 ` Nigel Cunningham
2007-07-10 17:45 ` Al Boldi
2007-07-10 18:20 ` Jeremy Maitin-Shepard
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=4691BD6F.8000809@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=jbms@cmu.edu \
--cc=linux-kernel@vger.kernel.org \
/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