All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Robert Stober <rstober@platform.com>
Cc: weiming <zephyr.zhao@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: A question no one can answer
Date: Fri, 15 Feb 2008 13:05:22 +0000	[thread overview]
Message-ID: <20080215130522.2c258316@core> (raw)
In-Reply-To: <3825A1772E68364B942CF6DBDF41C8BB04B8F3E3@catoexm06.noam.corp.platform.com>

On Thu, 14 Feb 2008 22:24:18 -0500
"Robert Stober" <rstober@platform.com> wrote:

> Weiming,
>  
> I agree that it is very hard, and that no one has done it. But
> nevertheless I suggest the following question to the Xen developers:
>  
> Given the fact that memory bandwidth is shared amongst multiple cores on
> a single die, assume that one VM is running on each core. What is to
> stop one VM from saturating the memory bus, causing reduced performance
> of all the other VMs? This is the general multi-core problem, not
> specific to Xen. But it affects Xen greatly. What use is it to allocate
> memory to a VM if it can't use the memory because a process of another
> VM has saturated the memory bus?

Its perfectly doable on modern x86 - you use the profiling registers and
set them up so you get a threshold interrupt when too much main memory
traffic is counted (which you use to reschedule punishing the memory
user). There are research papers on it from quite a long time back but
afaik nobody ever implemented it in production although its not too hard
to do so might be an interesting project.

Alan

  parent reply	other threads:[~2008-02-15 13:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15  2:27 A question no one can answer Robert Stober
2008-02-15  3:01 ` weiming
2008-02-15  3:24   ` Robert Stober
2008-02-15  3:32     ` weiming
2008-02-15 13:05     ` Alan Cox [this message]
2008-02-15 19:56       ` Dan Doucette
2008-02-15  8:25 ` Keir Fraser

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=20080215130522.2c258316@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=rstober@platform.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=zephyr.zhao@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.