From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: 贺鹏 <xnhp0320@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Is there any mechanism in XEN can use to limit the memory bandwidth of each domain?
Date: Mon, 6 Dec 2010 12:55:57 -0500 [thread overview]
Message-ID: <20101206175557.GB26693@dumpdata.com> (raw)
In-Reply-To: <AANLkTi=Wx6DcWngQ8m6cMcsYeirL9Ci7K=28EqQQsjFm@mail.gmail.com>
On Mon, Dec 06, 2010 at 06:00:14PM +0800, 贺鹏 wrote:
> Hi, all:
> As we all know, Xen can alloc different amount of memory to
> different VMs, but these VMs access memory by one shared memory bus, which
> means if one VM access the memory very frequently, the bandwidth of the
> memory shared by the other VM will decrease.
> So I'm wondering is there any mechanism in XEN can reserve the limit
> bandwidth of the memory for different VMs?
As in NUMA? There is work to make that be provided to Xen guests.
next prev parent reply other threads:[~2010-12-06 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 10:00 Is there any mechanism in XEN can use to limit the memory bandwidth of each domain? 贺鹏
2010-12-06 17:55 ` Konrad Rzeszutek Wilk [this message]
2010-12-07 10:58 ` George Dunlap
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=20101206175557.GB26693@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xnhp0320@gmail.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.