From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Juergen Schinker <ba1020@homie.homelinux.net>
Cc: mengxu@cis.upenn.edu, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [BUG] XEN-4.8-rc2 sched-rtds does not accept settings
Date: Tue, 18 Oct 2016 19:17:31 +0200 [thread overview]
Message-ID: <1476811051.6533.9.camel@citrix.com> (raw)
In-Reply-To: <20161018105114.GC23651@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2472 bytes --]
On Tue, 2016-10-18 at 11:51 +0100, Wei Liu wrote:
> CC Dario and Meng
>
Hi,
Thanks Wei for the Cc...
> On Mon, Oct 17, 2016 at 10:55:21PM +0100, Juergen Schinker wrote:
> >
> > xl -vf sched-rtds -v all -d 0 -p 20000 -b 8000
> >
> > whatever I set - the changes are not accepted and stay like you see
> > further down
> >
> > and the system feels very lame
> >
> > Cpupool Pool-0: sched=RTDS
> > Name ID Period Budget
> > Domain-0 0 10000 4000
> > zimbra 1 10000 4000
> > ethereum-os 2 10000 4000
> > mirot 3 10000 4000
> > wily 4 10000 4000
> >
Right, but what does the following shows:
xl sched-rtds -d 0 -v all
?
On my system, just using `xl sched-rtds` as above also still shows the
4000/10000 budget over period pairs, but adding '-v all' shows the
correct (i.e., the new) parameters.
In fact, the two commands are basically showing different things. I
agree it's not really clear, and I'll think to ways of improving the
situation (e.g., by improving the documentation, but also by making the
`xl' interface more consistent).
About the 'system feels lame', what does that exactly mean? Actually,
what is it that you are trying to achieve by using RTDS?
RTDS is a special purpose scheduler, and should be chosen for the
proper reasons and configured accurately. Typical use case is need for
deterministic/real-time scheduling of VMs.
Oh, and also, default parameters are 4000/10000=40% utilization. By
setting them to 8000/20000=40%, you're not changing much, at least
nothing that will be noticeable as a 'general system feeling', because
all domains (well, each vCPU of each domain), including dom0 (dom0's
vCPUs), are still limited to use at most 40% of pCPU time --although
with different periodicity.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-18 17:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 21:55 [BUG] XEN-4.8-rc2 sched-rtds does not accept settings Juergen Schinker
2016-10-18 10:51 ` Wei Liu
2016-10-18 17:17 ` Dario Faggioli [this message]
2016-10-18 17:41 ` Meng Xu
2016-10-18 18:52 ` Juergen Schinker
2016-10-18 19:06 ` Wei Liu
2016-10-18 21:49 ` Dario Faggioli
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=1476811051.6533.9.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=ba1020@homie.homelinux.net \
--cc=mengxu@cis.upenn.edu \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.