All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Emelyanov <xemul@parallels.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] [TECH TOPIC] live kernel patching
Date: Tue, 6 May 2014 17:23:14 +0400	[thread overview]
Message-ID: <5368E242.7090001@parallels.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1405060005290.3969@pobox.suse.cz>

On 05/06/2014 02:08 AM, Jiri Kosina wrote:
> On Mon, 5 May 2014, Andy Lutomirski wrote:
> 
>>> Tons of interest in this topic here, mostly for the in-memory database
>>> workloads.
>>
>> Would in-memory databases be happier if there were a way to kexec
>> without losing your data?
> 
> Well, that's basicaly what criu-based aproach is doing. With the drawback 
> that dumping during checkpointing can take a while for large tasks (such 
> as in-memory databases) I guess.

It does takes a while, but not when there's a lot of memory mapped by tasks.
This is what "preserving memory in place over kexec" is needed for -- we keep
all tasks' memory in memory, thus avoiding long delays due to writing it on
disk into images. Such thing performs poorly when there's a lot of _dirty_
memory hanging around.

Thanks,
Pavel

  parent reply	other threads:[~2014-05-06 13:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-02 19:42 [Ksummit-discuss] [CORE TOPIC] [TECH TOPIC] live kernel patching Jiri Kosina
2014-05-02 21:17 ` James Bottomley
2014-05-04  8:34 ` Li Zefan
2014-05-05 14:00 ` Chris Mason
2014-05-05 21:58   ` Andy Lutomirski
2014-05-05 22:08     ` Jiri Kosina
2014-05-06 13:17       ` James Bottomley
2014-05-06 13:23       ` Pavel Emelyanov [this message]
2014-05-06 14:07     ` Chris Mason
2014-05-06 15:44       ` Pavel Emelyanov
2014-05-06 17:02         ` Chris Mason
2014-05-06  1:33 ` Kees Cook
2014-05-06  7:05   ` Jiri Kosina
2014-05-06 13:16     ` Dave Jones
2014-05-06 13:23       ` Jiri Kosina
2014-05-06 13:18     ` Kees Cook
2014-05-06 13:28       ` James Bottomley
2014-05-06 13:41         ` Kees Cook
2014-05-06 17:11           ` Mimi Zohar
2014-05-06 18:34           ` James Bottomley
2014-05-06 12:30 ` Masami Hiramatsu

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=5368E242.7090001@parallels.com \
    --to=xemul@parallels.com \
    --cc=jkosina@suse.cz \
    --cc=ksummit-discuss@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.