From: Rusty Russell <rusty@rustcorp.com.au>
To: "King, Steven R" <steven.r.king@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: RE: yanked share, round 2
Date: Sat, 14 Jan 2006 14:34:11 +1100 [thread overview]
Message-ID: <1137209651.22193.20.camel@localhost.localdomain> (raw)
In-Reply-To: <44BDAFB888F59F408FAE3CC35AB4704102C66D7D@orsmsx409>
On Fri, 2006-01-13 at 15:02 -0800, King, Steven R wrote:
> How about combining both ideas: In order to map N pages from Xen's
> share pool, a DomU must provide N pages back to the pool. When a DomU
> unmaps (or crashes), it gets N pages back.
OK, early last year I hacked up a prototype implementation, which I'm
now bringing up-to-date with the modern Xen code, and some new
simplifications I'm toying with.
It's certainly a simple model to never have domains share their own
pages, and the hypervisor provide a DMA-like mechanism between domains
to allow bulk transfer. This would then page-swap if appropriate.
It makes drivers nice and simple, and avoids problems with starvation
et. al. Earlier results suggested it is competitive on benchmarks, too,
but it needs real testing under various loads.
Noone here should be surprised though, that I regard the simplicity of
the scheme as the most important factor.
Cheers!
Rusty.
--
ccontrol: http://ozlabs.org/~rusty/ccontrol
next prev parent reply other threads:[~2006-01-14 3:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 23:02 yanked share, round 2 King, Steven R
2006-01-14 0:21 ` Keir Fraser
2006-01-14 16:16 ` Mark Williamson
2006-01-14 3:34 ` Rusty Russell [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-13 21:25 King, Steven R
2006-01-13 21:31 ` Anthony Liguori
2006-01-14 16:15 ` Mark Williamson
2006-01-13 20:59 King, Steven R
2006-01-13 19:55 King, Steven R
2006-01-13 20:08 ` Keir Fraser
2006-01-14 16:21 ` Mark Williamson
2006-01-13 19:31 King, Steven R
2006-01-13 19:35 ` Anthony Liguori
2006-01-13 19:07 King, Steven R
2006-01-13 19:21 ` Keir Fraser
2006-01-13 19:23 ` Anthony Liguori
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=1137209651.22193.20.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=steven.r.king@intel.com \
--cc=xen-devel@lists.xensource.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 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.