From: Chris Mason <clm@fb.com>
To: Pavel Emelyanov <xemul@parallels.com>
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 13:02:57 -0400 [thread overview]
Message-ID: <536915C1.7020902@fb.com> (raw)
In-Reply-To: <53690340.4020007@parallels.com>
On 05/06/2014 11:44 AM, Pavel Emelyanov wrote:
> On 05/06/2014 06:07 PM, Chris Mason 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?
>>
>> Yes, for these apps we could just define a chunk of ram that was
>> supposed to stay the same after kexec and they would be happy.
>
> +1, I'd be happy to have this as well.
>
> One question about the chunk of memory you want to preserve -- is it anonymous
> memory or part of a page cache?
We have plain old memcached, and other fancier stuff is that is page
cache based. I think for memcached they've set it up to use shm so app
restarts don't toss the ram.
-chris
next prev parent reply other threads:[~2014-05-06 17:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 19:42 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
2014-05-06 14:07 ` Chris Mason
2014-05-06 15:44 ` Pavel Emelyanov
2014-05-06 17:02 ` Chris Mason [this message]
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=536915C1.7020902@fb.com \
--to=clm@fb.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--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