From: Todd Jones <stjones@cs.wisc.edu>
To: xen-devel@lists.sourceforge.net
Subject: Memory oversubscription
Date: Tue, 14 Sep 2004 17:39:19 -0500 [thread overview]
Message-ID: <41477317.4080004@cs.wisc.edu> (raw)
Hi. First of all, thanks for Xen. It's terrific!
I'm interested in doing memory oversubscription and am wondering if Xen
can do this (now or in the future).
For example, on a machine with 100MB available physical memory, can I:
1. Create a domain with a 90MB allocation
2. Inflate a balloon in that domain and return say 40MB back to Xen
I know there are mechanisms for doing 1 and 2...
3. Allocate a second domain with an allocation of 50MB?
Thanks,
--Todd
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
next reply other threads:[~2004-09-14 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 22:39 Todd Jones [this message]
2004-09-14 22:55 ` Memory oversubscription Keir Fraser
2004-09-23 21:06 ` Rik van Riel
2004-09-23 21:50 ` Ian Pratt
2004-09-23 22:08 ` Rik van Riel
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=41477317.4080004@cs.wisc.edu \
--to=stjones@cs.wisc.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.