From: Michael Vrable <mvrable@cs.ucsd.edu>
To: Xen-devel@lists.sourceforge.net
Subject: Re: Copy-on-write memory to allow many more xenU domains per machine
Date: Mon, 25 Oct 2004 15:38:10 -0700 [thread overview]
Message-ID: <20041025153810.A18297@cs.ucsd.edu> (raw)
In-Reply-To: <417CEDA6.6010209@thegreen.co.uk>; from mpah@thegreen.co.uk on Mon, Oct 25, 2004 at 01:12:22PM +0100
On Mon, Oct 25, 2004 at 01:12:22PM +0100, Peri Hankey wrote:
> Some time ago Michael Vrable talked about copy-on-write memory to enable
> large numbers of nearly identical machines to run on the same physical
> hardware. Is this a feasible proposition? I asked a few days ago in the
> original thread, but no-one seems to have noticed. It seems to me that
> it would be a very significant feature to offer.
I'm still around, though a bit slow to respond.
Ian mentioned that honeypots are one the scenarios where copy-on-write
sharing of memory makes a lot of sense; that's the reason that I'm
trying implement it. I hope, of course, that if I do manage to get
something working it would be useful in other scenarios as well.
My current status: I've been working first on using shadow page tables
to hide the actual machine addresses of pages from domains. I'm only
partway through doing that, and may yet go back and change how I'm
approaching that (I'm still learning bits about how Xen works as I'm
going through to modify the code; I'm also thinking now of changes that
would be good to make copy-on-write easier later). I'm trying to write
up some of my design thoughts; if anyone here is interested or would
like to offer comments, I can post that here.
David mentioned implementing a clone() for VMs; that is something that
I'd also like to try out. (It should be possible to test that after
only the first step of hiding machine addresses, before copy-on-write is
implemented, though copy-on-write will make it efficient.)
If someone else beats me to getting this implemented, I suppose I can't
complain. But if this is an area that isn't getting much current work,
and I'm able to contribute (a hopefully clean implementation that others
wouldn't mind using), that would be great.
--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
next prev parent reply other threads:[~2004-10-25 22:38 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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
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=20041025153810.A18297@cs.ucsd.edu \
--to=mvrable@cs.ucsd.edu \
--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.