All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Neugebauer <rolf.neugebauer@intel.com>
To: Brian Wolfe <brianw@terrabox.com>
Cc: rolf.neugebauer@intel.com, xen-devel@lists.sourceforge.net
Subject: Re: Xen cpu usage limting
Date: Fri, 16 Apr 2004 17:54:08 +0100	[thread overview]
Message-ID: <1082134448.13745.46.camel@wyvis> (raw)
In-Reply-To: <41749.216.166.50.35.1082133605.squirrel@216.166.50.35>

Hi Brian,

which version of Xen/Xenolinux are you using? the scheduler
implementation changed from 1.2 to 1.3-unstable.

On Fri, 2004-04-16 at 17:40, Brian Wolfe wrote:
> Is it possible? How? (looked for documentation, but I didn't see any.)
> I did see xen_cpuperf, but I can't get any real information from there
> either. 8-(
> 
> I have 8 domains (including domain-0) runing on the server. If one goes to
> 100% cpu time, the system bogs. I'd like to be able to ensure that each
> instance can't keep the rest from runing...

This should definitely not happen!!! Could you provide a little more
detail on what is running in the different domains? 

In 1.2 the scheduler is a weighted proportional share scheduler (BVT)
and by default all domains get the same weight and therefore should get
the same share.

in 1.3 you have a boot-time choice between schedulers, BVT (same as in
1.2, Atropos (a soft real time scheduler based on EDF)

I have just tested with 1.3-unstable, four domains on a dual processor
machine (two domains per CPU) and BVT as the scheduler and they happily
share the CPU 50/50 if both run the equivalent of a while(1) loop.

Rolf





-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  parent reply	other threads:[~2004-04-16 16:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 16:40 Xen cpu usage limting Brian Wolfe
2004-04-16 16:47 ` Keir Fraser
2004-04-16 16:54 ` Rolf Neugebauer [this message]
2004-04-16 17:14   ` Brian Wolfe
2004-04-16 17:19     ` Keir Fraser
2004-04-16 17:32     ` Mark Williamson
2004-04-16 17:52       ` Brian Wolfe
2004-04-16 19:14         ` Ian Pratt
2004-04-16 22:47           ` Brian Wolfe
2004-04-19 15:40         ` Mark Williamson
2004-04-19 17:26           ` Brian Wolfe
2004-04-19 17:34             ` Mark Williamson
2004-04-19 18:57               ` Brian Wolfe
2004-04-20 15:44       ` Need help I RATTAN
2004-04-20 16:27         ` Borut Mrak
2004-04-20 18:02         ` I RATTAN
2004-04-20 18:23           ` Rolf Neugebauer
2004-04-21  0:24         ` I RATTAN
2004-04-16 17:17 ` Xen cpu usage limting Mark Williamson

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=1082134448.13745.46.camel@wyvis \
    --to=rolf.neugebauer@intel.com \
    --cc=brianw@terrabox.com \
    --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.