From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: xemul@parallels.com
Cc: linux-mm@kvack.org
Subject: Re: [LSF/MM TOPIC][ATTEND] cleancache extension and memory checkpoint/restore
Date: Thu, 2 Feb 2012 16:32:32 -0800 (PST) [thread overview]
Message-ID: <abfed6dd-a194-4feb-b12e-735f9918804d@default> (raw)
Hi Pavel --
> From: Pavel Emelyanov <xemul () parallels ! com>
> 1. cleancache extension
> In containerized systems, when containers are more or less equal to each
> other, we can save RAM and (!) disk IOPS if we share equal files between
> containers. We've been using a unionfs-like approach and faced several
> disadvantages of it (I can describe them in details if required).
> Now we're working on extending the cleancache subsystem to achieve this
> sharing. The cost of fully isolated filesystems is very high, I can provide
> numbers of various performance experiments, thus this is required badly for
> containers.
I agree this is a great use of cleancache!
FYI, the Xen implementation of transcendent memory optionally
does deduplication. I think you are probably doing something
very similar so you may be able to leverage some code. No changes
to cleancache are needed... you just need to register a different
"backend" (e.g. like zcache or RAMster or the Xen tmem stubs).
IIRC, the Xen implementation is much simpler than KSM because
the candidate pages are more closely managed.
Hopefully we can talk about it at LSF/MM!
Dan
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2012-02-03 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 0:32 Dan Magenheimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-02-02 13:37 [LSF/MM TOPIC][ATTEND] cleancache extension and memory checkpoint/restore Pavel Emelyanov
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=abfed6dd-a194-4feb-b12e-735f9918804d@default \
--to=dan.magenheimer@oracle.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).