All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Diestelhorst <sd386@cam.ac.uk>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: Dan Magenheimer <dan.magenheimer@hp.com>, xen-devel@lists.xensource.com
Subject: Re: Re: IDLE domain is scheduled more than dom0
Date: Sat, 09 Jul 2005 19:14:06 +0100	[thread overview]
Message-ID: <42D013EE.7060209@cam.ac.uk> (raw)
In-Reply-To: <200507081133.02927.habanero@us.ibm.com>

Andrew Theurer schrieb:

>On Friday 08 July 2005 09:53, Dan Magenheimer wrote:
>  
>
>>>	Shouldn't IDLE domain not be scheduled for most time? Because
>>>idle task will call into PAL for power save on XEN/IA64, the
>>>performance is really, really bad to boot Dom0. The net effect is
>>>about ten times slower. After adding "sched=bvt", everything back
>>>to normal.
>>>      
>>>
>>If the sedf scheduler is scheduling the idle domain when
>>domain0 is runnable, surely this is affecting performance
>>on x86 also and is a bug that should be fixed?
>>
>>Has anyone done any performance testing (on x86) since
>>sedf was checked in as the default?
>>    
>>
>
>Just tried launching some cpu bound tasks in dom0, and I get only 75% 
>cpu util for dom0.  I'll try the other domain scheduler and see if it 
>clears it up.
>
>-Andrew
>
>
> cpu0:  [075.3] d0-0[075.3]
> cpu1:  [075.3] d0-1[075.3]
> cpu2:  [075.3] d0-2[075.3]
> cpu3:  [074.8] d0-3[074.8]
>  
>
This is the current default behaviour of domain 0, it gets 75% of the
CPU time and no slack time. This is easily changeable, and I guess it is
usefull to do so!
Stephan

  parent reply	other threads:[~2005-07-09 18:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-08  9:44 IDLE domain is scheduled more than dom0 Tian, Kevin
2005-07-08 14:53 ` Dan Magenheimer
2005-07-08 16:33   ` Andrew Theurer
2005-07-08 16:40     ` Andrew Theurer
2005-07-08 19:06       ` Bin Ren
2005-07-09 18:17         ` Stephan Diestelhorst
2005-07-09 18:28           ` Bin Ren
2005-07-09 18:14     ` Stephan Diestelhorst [this message]
2005-07-10 17:14       ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-07-08 19:22 Magenheimer, Dan (HP Labs Fort Collins)
2005-07-09 19:32 Magenheimer, Dan (HP Labs Fort Collins)
2005-07-10 17:17 Ian Pratt
2005-07-12  4:10 Tian, Kevin
2005-07-12 11:38 Tian, Kevin
2005-07-12 12:24 ` Stephan Diestelhorst

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=42D013EE.7060209@cam.ac.uk \
    --to=sd386@cam.ac.uk \
    --cc=dan.magenheimer@hp.com \
    --cc=habanero@us.ibm.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.