From: Peri Hankey <mpah@thegreen.co.uk>
To: Michael Vrable <mvrable@cs.ucsd.edu>
Cc: Xen-devel@lists.sourceforge.net
Subject: Re: Shadow page tables?
Date: Thu, 21 Oct 2004 09:38:01 +0100 [thread overview]
Message-ID: <41777569.7060907@thegreen.co.uk> (raw)
In-Reply-To: <20041012115013.B16621@cs.ucsd.edu>
Hello
Some time ago you talked about copy-on-write memory to enable large
numbers of nearly identical machines to run on the same physical
hardware. I have also thought about that - after all equivalent
mechansisms already exist to provide copy-on-write semantics for process
forking (and also I think in the /proc/mm mechanisms used in some
versions of UML separate kernel address space (SKAS) handling).
Have you advanced along this path, or is anyone actively doing that? The
problem you found the other day suggests that you were looking pretty
closely at code that relates to this question. My very crude
understanding is that one would want to share the physical memory
allocation that is currently given to a single xenU domain between a
group of xenU domains each of which has its own copy-on-write mapping
that starts from a read-only image that is shared between all of them.
The table grant mehanism would need to understand the relationship
between members of such a group of domains. But as I say, this is still
very hazy to me.
On the other point you raised, about copy-on-write filesystem images, I
looked at evms2 (http://evms.sourceforge.net/), which sits above lvm2
and other systems and offers its own snapshot feature. It is only usable
on disks that it controls, so you either have to use a separate disk
from the one you boot from, or you have to use an initrd to be able to
boot from an evms volume. The snapshot feature seemed 'snappier' (I was
able to create a number of snapshot objects and activate them without
memory problems of the kind that I encountered with lvm2 snapshots).
However it didn't seem possible to make it provide multiple persistent
writable snapshots of the kind that would support multiple xenU domains
where each uses its own copy-on-write image of an underlying readonly
root filesystem. Did I miss something? Has anyone else tried using evms
for these purposes?
I saw Ian's comments about gnbd and csnap
(http://sources.redhat.com/cluster/), but it seems that the csnap
mechanism is in a pretty early state of development.
Regards
Peri
Michael Vrable wrote:
Michael Vrable wrote:
>On Fri, Oct 08, 2004 at 10:11:18AM +0100, Keir Fraser wrote:
>
>
>>We intend to flesh out the shadow p.t. code a little mroe to support
>>full memory virtualisation. It's not there yet, but it won't require
>>an enormous amount of code to get it going.
>>
>>
>
>Any idea what the time frame for this is? I was considering taking a
>stab at it myself, but don't want to duplicate work.
>
>My longer term goal is to try to get copy-on-write sharing of memory
>pages between domains and to see how far Xen can scale in running many
>nearly-identical virtual machines. To implement this, however, will
>require (at least as I've thought it through) memory virtualization. So
>that was the first thing I was planning to work on.
>
>If no one else was actively working on this, I'm happy to discuss the
>design and contribute what I end up with. (Both for the memory
>virtualization and the copy-on-write work.)
>
>(This is also the reason for my interest in copy-on-write disks, though
>it's looking like LVM may be too heavyweight for supporting large
>numbers of VMs.)
>
>--Michael Vrable
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
>Use IT products in your business? Tell us what you think of them. Give us
>Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
>http://productguide.itmanagersjournal.com/guidepromo.tmpl
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
>
>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
next prev parent reply other threads:[~2004-10-21 8:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 8:59 Shadow page tables? Chengyuan Li
2004-10-08 9:11 ` Keir Fraser
2004-10-10 2:52 ` Chengyuan Li
2004-10-12 18:50 ` Michael Vrable
2004-10-12 20:09 ` Andrew Warfield
2004-10-13 1:53 ` Michael Vrable
2004-10-21 8:38 ` Peri Hankey [this message]
2004-10-25 12:12 ` Copy-on-write memory to allow many more xenU domains per machine Peri Hankey
2004-10-25 12:21 ` Ian Pratt
2004-10-25 18:24 ` David Hopwood
2004-10-25 19:52 ` Ronald G. Minnich
2004-10-25 20:19 ` Ian Pratt
2004-10-25 22:38 ` Michael Vrable
2004-10-26 8:15 ` Peri Hankey
2004-10-26 18:30 ` Michael Vrable
2004-10-26 19:43 ` Ian Pratt
2004-10-26 22:19 ` Michael Vrable
2004-11-02 20:55 ` Jacob Gorm Hansen
2004-11-02 21:33 ` Ian Pratt
2004-11-02 21:50 ` urmk
-- strict thread matches above, loose matches on Subject: below --
2004-10-10 8:55 Shadow page tables? Ian Pratt
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=41777569.7060907@thegreen.co.uk \
--to=mpah@thegreen.co.uk \
--cc=Xen-devel@lists.sourceforge.net \
--cc=mvrable@cs.ucsd.edu \
/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.