public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Concannon <mike@concannon.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: lokum spand <lokumsspand@hotmail.com>, linux-kernel@vger.kernel.org
Subject: Re: A possible idea for Linux: Save running programs to disk
Date: Sat, 01 Oct 2005 18:21:37 -0400	[thread overview]
Message-ID: <433F0BF1.2020900@concannon.net> (raw)
In-Reply-To: <1128202754.8153.0.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>On Sat, 2005-10-01 at 13:30 -0800, lokum spand wrote:
>  
>
>>I allow myself to suggest the following, although not sure if I post in
>>the right group:
>>
>>Suppose Linux could save the total state of a program to disk, for
>>instance, imagine a program like mozilla with many open windows. I give
>>it a SIGNAL-SAVETODISK and the process memory image is dropped to a
>>file. I can then turn off the computer and later continue using the
>>program where I left it, by loading it back into memory.
>>
>>Would that be possible? At least a program can be given a ctrl-z and is
>>    
>>
>
>there is a LOT of state though.. the moment you add networking in the
>picture the amount of state just isn't funny anymore. Your X example is
>a good one as well...
>  
>
There are a few cluster/parallel computing libraries out there that are 
starting to allow "process migration"...

One would assume that "saving it to a disk" is simply a degenerate case 
of migrating the process...

Presuming they have process migration working (and it seemed close a 
while ago when I last looked), saving to a file might already be 
supported...  I'd google "process migration" and you are likely to find 
a lot of discussion on this topic...

/mike

>-
>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/
>
>  
>


  reply	other threads:[~2005-10-01 22:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 21:30 A possible idea for Linux: Save running programs to disk lokum spand
2005-10-01 21:39 ` Arjan van de Ven
2005-10-01 22:21   ` Michael Concannon [this message]
2005-10-01 22:51     ` lokum spand
2005-10-01 23:09       ` Michael Concannon
2005-10-02  8:30       ` Tomasz Torcz
2005-10-02 13:31       ` Benoit Boissinot
2005-10-02 18:49       ` Jon Masters
2005-10-02 19:21       ` Lexington Luthor
2005-10-02  0:34   ` grundig
2005-10-02  4:53 ` Bernard Blackham
2005-10-02 12:57   ` Ed Tomlinson
2005-10-02 14:16     ` Bernard Blackham
2005-10-10  1:13       ` serue
2005-11-06 15:42         ` Bernard Blackham
2005-11-09  2:15           ` Peter Chubb
2005-10-02  5:36 ` Andrew Haninger
2005-10-03 17:41   ` Adrian Bunk
2005-10-03 18:52     ` Andrew Haninger
2005-10-03 18:59       ` Adrian Bunk
2005-10-03 19:48         ` Andrew Haninger
2005-10-02 18:46 ` Jon Masters
     [not found] <4SXfo-7hM-9@gated-at.bofh.it>
2005-10-02  3:19 ` Bodo Eggert
     [not found] ` <4T47e-5E-1@gated-at.bofh.it>
     [not found]   ` <4TbLq-2VG-5@gated-at.bofh.it>
     [not found]     ` <4TcR9-4sS-9@gated-at.bofh.it>
2005-10-02 17:08       ` Bodo Eggert
2005-10-02 17:51         ` Bernard Blackham
2005-10-02 19:13           ` Jeff Dike
2005-10-03 20:02           ` 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=433F0BF1.2020900@concannon.net \
    --to=mike@concannon.net \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lokumsspand@hotmail.com \
    /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