From: Peri Hankey <mpah@thegreen.co.uk>
Cc: Xen-devel@lists.sourceforge.net
Subject: Copy-on-write memory to allow many more xenU domains per machine
Date: Mon, 25 Oct 2004 13:12:22 +0100 [thread overview]
Message-ID: <417CEDA6.6010209@thegreen.co.uk> (raw)
In-Reply-To: <20041012115013.B16621@cs.ucsd.edu>
Hello
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.
Regards
Peri
-------------------------------------------------------
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 12:12 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 ` Peri Hankey [this message]
2004-10-25 12:21 ` Copy-on-write memory to allow many more xenU domains per machine 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
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=417CEDA6.6010209@thegreen.co.uk \
--to=mpah@thegreen.co.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.