All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Ackaouy <ack@xensource.com>
To: Atsushi SAKAI <sakaia@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [Q] about Credit Scheduler Dom0 Scheduling policy.
Date: Thu, 26 Oct 2006 09:42:11 +0100	[thread overview]
Message-ID: <20061026084210.GA3497@cockermouth.uk.xensource.com> (raw)
In-Reply-To: <200610260835.k9Q8ZvZZ025347@fjmscan502.ms.jp.fujitsu.com>

Thanks.

That indicates the dom0 and I/O generating domU are preempting
the spinners but not each other and are therefore running
optimally.

That is great news.

On Thu, Oct 26, 2006 at 05:35:20PM +0900, Atsushi SAKAI wrote:
> Hi, Emmanuel
> 
> Sorry for mis-reading it.
> 
> The measured value to omit 2 SPIN DomU is same as w/ 2SPIN DomU.
> 
> Result 
> 
>  44
> 133
> 533
> (Kbps)
> 
> And xentop says 
> the CPU usage for Dom0 DomU3 is same as w/ 2 SPIN DomU
> (Both Dom0 and DomU3 usages are 1.0 to 1.2 % ) 
> 
> Thanks,
> Atsushi SAKAI
> 
> >The bench mark is same as previous one.
> >
> >Only Dom0 and DomU3 are no spinning vcpus.
> >Other DomU1 and DomU2 are spinning vcpus.
> >
> >#pcpu(s)=1
> >#vcpu(s)=2(no spinning)
> >#vcpu(s)=2(spinning)
> >#vcpu(s)=4(total spinning and no spinning)
> >
> >>
> >>Out of curiosity, what are the numbers like when running this
> >>benchmark with no spinning VCPUs competing?
> >>
> >>> With this patches, the CREDIT scheduler changed for I/O aware.
> >>> (At vcpu_wake, the priority changes from UNDER to BOOST,
> >>> At vcpu_acct, the priority changes from BOOST to UNDER.) 
> >>> 
> >>> It seems reasonable fixes!
> >>> But I am afraid many I/O intensive GuestOSes are running.
> >>> (I hope this prospect is needless fear.)
> >>
> >>I've been careful to prevent BOOSTed VCPUs from taking over the
> >>system or otherwise impacting fairness:
> >>
> >>- Only VCPUs with positive credits can be boosted.
> >>- While boosted, a VCPU is charged for any substential CPU
> >>  resources consumed.
> >>- VCPUs can run uninterrupted with a boosted priority for no
> >>  more than 10ms (1/3-rd of a full time slice).
> >>
> >>Only VCPUs which consume a negligeable amount of CPU resources
> >>should get real benefit from boosting. When multiple VCPUs are
> >>boosted, they will round robin or be queued FIFO. The idea is
> >>for a boosted VCPU to preempt spinners but not other boosted
> >>I/O intensive guests. A VCPU cannot use the boosting mechanism
> >>to consume more CPU than its allocated fair share.
> >
> >I agree.
> >
> >Thanks
> >Atsushi SAKAI
> >
> >
> >
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@lists.xensource.com
> >http://lists.xensource.com/xen-devel
> >
> 
> 
> 
> 
> 

  reply	other threads:[~2006-10-26  8:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18 11:49 [Q] about Credit Scheduler Dom0 Scheduling policy Atsushi SAKAI
2006-10-18 13:11 ` Emmanuel Ackaouy
2006-10-18 13:24   ` Emmanuel Ackaouy
2006-10-23  4:13     ` Atsushi SAKAI
2006-10-23 14:32       ` Emmanuel Ackaouy
2006-10-24  6:46         ` Atsushi SAKAI
2006-10-24  9:49           ` Emmanuel Ackaouy
2006-10-25 10:29           ` Emmanuel Ackaouy
2006-10-25 13:02             ` Atsushi SAKAI
2006-10-25 14:03               ` Emmanuel Ackaouy
2006-10-26  6:15                 ` Atsushi SAKAI
2006-10-26  8:35                   ` Atsushi SAKAI
2006-10-26  8:42                     ` Emmanuel Ackaouy [this message]
2006-10-26 12:52                       ` Pasi Kärkkäinen
2006-10-26 13:04                         ` Emmanuel Ackaouy
2006-10-26 13:47                           ` Pasi Kärkkäinen

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=20061026084210.GA3497@cockermouth.uk.xensource.com \
    --to=ack@xensource.com \
    --cc=sakaia@jp.fujitsu.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.