From: Marco Stornelli <marco.stornelli@gmail.com>
To: Vladimir Davydov <vdavydov@parallels.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, criu@openvz.org, devel@openvz.org,
xemul@parallels.com
Subject: Re: [PATCH RFC] pram: persistent over-kexec memory file system
Date: Sat, 27 Jul 2013 17:41:30 +0200 [thread overview]
Message-ID: <51F3EA2A.3090905@gmail.com> (raw)
In-Reply-To: <1374841763-11958-1-git-send-email-vdavydov@parallels.com>
Il 26/07/2013 14:29, Vladimir Davydov ha scritto:
> Hi,
>
> We want to propose a way to upgrade a kernel on a machine without
> restarting all the user-space services. This is to be done with CRIU
> project, but we need help from the kernel to preserve some data in
> memory while doing kexec.
>
> The key point of our implementation is leaving process memory in-place
> during reboot. This should eliminate most io operations the services
> would produce during initialization. To achieve this, we have
> implemented a pseudo file system that preserves its content during
> kexec. We propose saving CRIU dump files to this file system, kexec'ing
> and then restoring the processes in the newly booted kernel.
>
http://pramfs.sourceforge.net/
Marco
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-07-27 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 12:29 [PATCH RFC] pram: persistent over-kexec memory file system Vladimir Davydov
2013-07-27 15:41 ` Marco Stornelli [this message]
2013-07-27 17:35 ` Vladimir Davydov
2013-07-27 17:37 ` Marco Stornelli
2013-07-28 10:05 ` Vladimir Davydov
2013-07-28 11:02 ` Marco Stornelli
2013-07-28 14:31 ` Vladimir Davydov
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=51F3EA2A.3090905@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=criu@openvz.org \
--cc=devel@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov@parallels.com \
--cc=xemul@parallels.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;
as well as URLs for NNTP newsgroup(s).