From: "eric miao" <eric.y.miao@gmail.com>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Kernel Newbies" <kernelnewbies@nl.linux.org>
Subject: Re: RFC: Self-snapshotting in Linux
Date: Wed, 16 Apr 2008 16:49:11 +0800 [thread overview]
Message-ID: <f17812d70804160149q1fc694dtdff26e3650666c16@mail.gmail.com> (raw)
In-Reply-To: <804dabb00804160144j25584229t6673bc182fa13b3@mail.gmail.com>
Hibernation maybe ... try "echo "disk" > /sys/power/state"
On Wed, Apr 16, 2008 at 4:44 PM, Peter Teoh <htmldeveloper@gmail.com> wrote:
> Sorry if this is a a crazy idea.....just be forewarned....
>
> First, I would like to make a reference to VMWare's snapshot (name not
> important, emphasize the idea) feature - hopefully u are familiar with
> it. This is a feature whereby u can freeze the entire OS (kernel +
> userspace application running) and then later reload itself next time,
> continuing where it left off, without reboot from ground zero.
>
> Next, can I ask, is such a feature useful in Linux? Ie, able to
> restart the kernel + userspace application from where u left off, the
> last time round. Not JUST the normal suspend/resume feature, but
> more important able to CHOOSE among the different available images for
> u to resume on. Eg, u want to freeze the current 2.6.25-rc6 kernel,
> save it, and then restore back the 2.6.23-rc5 image, work on it, save
> it, and then restore the previous image again. All done without
> virtualization as in the VMWare sense - which really is CPU intensive
> and slow things down a lot. Now we can directly execute each OS
> kernel image on the CPU, and since saving and restoring is quite fast
> (eg, zipping up the entire physical memory before saving into
> permanent storage) - I supposed this will be much faster than the
> normal initialization/fsck work done normally....or did I missed out
> anything?
>
> Essentially, to reiterate the key idea: able to snapshot the current
> kernel+userspace permanent.....restore from another snapshot....and
> then switch back again if needed etc.....will the implementation be
> difficult...if not impossible????
>
> --
> Regards,
> Peter Teoh
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Cheers
- eric
next prev parent reply other threads:[~2008-04-16 8:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 8:44 Peter Teoh
2008-04-16 8:49 ` eric miao [this message]
2008-04-16 9:49 ` Ben Nizette
2008-04-16 10:33 ` Scott Lovenberg
2008-04-16 11:14 ` Pavel Machek
[not found] ` <804dabb00804160821n4872c65fh44f2c07ead67fc49@mail.gmail.com>
2008-04-17 9:33 ` Pavel Machek
2008-04-16 18:31 ` Greg Freemyer
[not found] <ajbvb-3Ur-21@gated-at.bofh.it>
[not found] ` <ajcri-65w-13@gated-at.bofh.it>
2008-04-16 10:27 ` Alan Jenkins
2008-04-16 11:12 ` Pavel Machek
2008-04-16 13:50 ` Alan Jenkins
2008-04-17 9:32 ` Pavel Machek
2008-04-19 16:42 ` Alan Jenkins
2008-04-17 0:55 ` Nigel Cunningham
2008-04-17 7:48 ` Alan Jenkins
[not found] ` <ajd42-7Gt-49@gated-at.bofh.it>
2008-04-16 11:02 ` Alan Jenkins
2008-04-16 15:06 ` Peter Teoh
2008-04-16 16:21 ` Disconnect
2008-04-16 19:50 ` Vivek Goyal
[not found] ` <48065C64.7010808@gmail.com>
2008-04-16 20:10 ` Scott Lovenberg
2008-04-16 20:25 ` Vivek Goyal
2008-04-17 2:09 ` Scott Lovenberg
2008-04-17 6:23 ` Peter Teoh
2008-04-17 8:43 ` Alan Jenkins
2008-04-17 16:01 ` Scott Lovenberg
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=f17812d70804160149q1fc694dtdff26e3650666c16@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=htmldeveloper@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--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
all inboxes | Powered by JetHome®