From: Niraj Tolia <ntolia@hotmail.com>
To: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Seamlessly sharing identical memory pages among domains
Date: Fri, 21 May 2004 01:52:47 -0400 [thread overview]
Message-ID: <40AD992F.3070606@hotmail.com> (raw)
In-Reply-To: <E1BQyfa-00055Y-00@mta1.cl.cam.ac.uk>
While not exactly related, this paper
<http://www.cs.rice.edu/~ssiyer/r/superpages/osdi02superpages/> (Section
4.7) presented at OSDI'02 showed that there was significant overhead
when trying to detect dirty pages using SHA-1 hash digests. It would be
interesting to see if this applied to Xen.
Niraj
--
http://www.andrew.cmu.edu/~ntolia
Ian Pratt wrote:
>>I'd like to know if XEN is or will be implementing any mechanism for
>>transparently sharing pages with identical content among domains, to
>>minimize memory consumption, similar to what is implemented in VMWare's
>>ESX server (chapter 4 of the paper whose link is below).
>
>
> I'm not convinced there's that much sharing to be had between
> VMs: One side effect of implementing some test code for live
> migration was that I collected some traces containing crc
> fingerprints of the memory pages of several domains. There
> weren't many hashes in common. Perhaps this shouldn't be
> surprising -- application text is typically small compared to the
> heap data they operate on. The actual datasets operated on by
> domains are typically distinct.
>
> However, there might be some value in having a shared read-only
> buffer cache, if only for the saved IO ops. Implementing a cache
> that replicates pages in memory (rather than sharing) is trivial.
>
> Doing a proper shared cache is slightly trickier given the
> paravirtualised memory interface -- we'd have to introduce guests
> to a new kind of write fault: "A write fault has occurred, and
> you'll have to copy the page because this machine page is
> immutable as it is already shared with other domains". Modifying
> Linux to handle this wouldn't be hard.
>
> Of course, if you're running a domain on Xen's shadow page tables
> then all of this manipulation is easy and can be done
> transparently to the domain. Of course, you pay a performance
> penalty...
>
> Ian
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
next prev parent reply other threads:[~2004-05-21 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 13:18 Seamlessly sharing identical memory pages among domains Scheer, Roque
2004-05-21 1:17 ` Ian Pratt
2004-05-21 3:58 ` Kip Macy
2004-05-21 6:56 ` Ian Pratt
2004-05-21 11:21 ` Kip Macy
2004-05-21 5:52 ` Niraj Tolia [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-21 11:56 Scheer, Roque
2004-05-21 12:05 ` Ian Pratt
2004-05-21 12:08 ` Steven Hand
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=40AD992F.3070606@hotmail.com \
--to=ntolia@hotmail.com \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.