From: Avi Kivity <avi@argo.co.il>
To: Michael Buesch <mb@bu3sch.de>
Cc: Pau Garcia i Quiles <pgquiles@elpauer.org>, linux-kernel@vger.kernel.org
Subject: Re: [IDEA] Poor man's UPS
Date: Mon, 22 May 2006 11:19:48 +0300 [thread overview]
Message-ID: <44717424.4020705@argo.co.il> (raw)
In-Reply-To: <200605212146.30342.mb@bu3sch.de>
Michael Buesch wrote:
>> > The "continuous hibernation" is some kind of memory snapshots taken, say,
>> > every 5 minutes. The next time your system starts after a crash, it'd say "oh
>>
>
> You really want a system, which freezes for 10-20 seconds every 5 minutes,
> and thaws again when the image is written?
>
The snapshot could be taken in the background, by marking all pages
read-only, starting a thread to write them to disk, and continuing
normal processing.
Such systems have been implemented in the past, see for example
http://www.eros-os.org/.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2006-05-22 8:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 19:31 [IDEA] Poor man's UPS Pau Garcia i Quiles
2006-05-21 19:38 ` Dave Jones
2006-05-21 19:46 ` Michael Buesch
2006-05-22 8:19 ` Avi Kivity [this message]
2006-05-22 10:54 ` Jan Engelhardt
2006-05-21 22:40 ` Christian Trefzer
2006-05-22 13:04 ` Jan Knutar
2006-05-22 13:29 ` linux-os (Dick Johnson)
2006-05-22 15:25 ` Christian Trefzer
2006-05-22 15:54 ` linux-os (Dick Johnson)
2006-05-22 19:34 ` Christian Trefzer
2006-05-22 15:13 ` Christian Trefzer
2006-05-22 15:40 ` Alan Cox
2006-05-22 15:48 ` Christian Trefzer
2006-05-22 16:15 ` Matthias Schniedermeyer
2006-05-22 19:40 ` Christian Trefzer
2006-05-22 19:45 ` Avi Kivity
2006-05-23 2:02 ` Martin J. Bligh
2006-05-22 19:46 ` Nuri Jawad
2006-05-22 22:40 ` Christian Trefzer
2006-05-22 17:05 ` Jeff V. Merkey
2006-05-21 23:02 ` Neil Brown
2006-05-22 0:08 ` Chris Wedgwood
2006-05-22 0:23 ` Neil Brown
2006-05-22 1:29 ` Björn Steinbrink
2006-05-22 1:44 ` Neil Brown
2006-05-22 9:29 ` 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=44717424.4020705@argo.co.il \
--to=avi@argo.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=pgquiles@elpauer.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