xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Andrii Anisov <andrii_anisov@epam.com>
Subject: Re: RT-Xen on ARM
Date: Wed, 12 Jul 2017 08:13:01 +0200	[thread overview]
Message-ID: <1499839981.7756.11.camel@citrix.com> (raw)
In-Reply-To: <CAENZ-+mhn6=Ta9xfUsumNW_wTsR5KJ9p78CQkRDWS=uQ8ivbxQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1740 bytes --]

On Fri, 2017-07-07 at 14:29 -0400, Meng Xu wrote:
> On Wed, Jul 5, 2017 at 4:29 AM, Dario Faggioli
> <dario.faggioli@citrix.com> wrote:
> > 
> The total utilization can help answer if the VCPU parameters are
> feasible or not.
>
I'm just saying that we could keep track of utilization and, if on an
host with N CPUs, we reach more than (N*100)%, we can warn the user
that deadlines will be missed.

This is a simple enough check, and it can live in the hypervisor.

> But I'm thinking there may exist a better (yet optimal) approach to
> answer the question: If all VCPUs on K cores are globally scheduled
> or
> completely partitioned onto each of the K cores, we can use
> Utilization Bound of the EDF scheduling algorithm for checking if the
> VCPU's performance can be safely provided.
> This requires the VCPUs' parameters (which also computes the total
> utilization), which are easy to get.
> 
I know there's math we can use, I'm just saying we don't want that in
Xen.

> Another thing is where this schedulability check should be provided:
> in Xen kernel, in Xen toolstack, or as a separate utility tool?
> In my opinion, a separate utility tool seems to be better than the
> other tool approaches?
> 
Exactly. As said above, you don't put something as complex as that
inside Xen. It can well live in toolstack, IMO, as far as we also add a
(global, non per-domain) for telling whether we want admission or
control not.

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

  reply	other threads:[~2017-07-12  6:13 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 11:03 RT-Xen on ARM Andrii Anisov
2017-07-03 13:03 ` Wei Liu
2017-07-03 13:26   ` Andrii Anisov
2017-07-03 13:35 ` Meng Xu
2017-07-03 14:58   ` Andrii Anisov
2017-07-03 18:42     ` Meng Xu
2017-07-04 12:28       ` Andrii Anisov
2017-07-04 15:12         ` Meng Xu
2017-07-05  8:29           ` Dario Faggioli
2017-07-07 18:29             ` Meng Xu
2017-07-12  6:13               ` Dario Faggioli [this message]
2017-07-05  8:42         ` Dario Faggioli
2017-07-05  8:51       ` Dario Faggioli
2017-07-07 18:43         ` Meng Xu
2017-07-07 18:46           ` Meng Xu
2017-07-10  9:22           ` Andrii Anisov
2017-08-01 11:02     ` Andrii Anisov
2017-08-18 20:43       ` Meng Xu
2017-08-21  8:07         ` Andrii Anisov
2017-08-21  8:16           ` Andrii Anisov
2017-08-22  2:02             ` Meng Xu
2017-09-27 12:37               ` Andrii Anisov
2017-09-27 13:57                 ` Meng Xu
2017-09-27 14:37                   ` Andrii Anisov
2017-09-27 19:57                     ` Meng Xu
2017-09-28  9:18                       ` Andrii Anisov
2017-09-28 16:01                         ` Dario Faggioli
2017-09-28 17:56                           ` Dario Faggioli
2017-09-29 10:24                           ` Andrii Anisov
2017-10-09 15:38                         ` Meng Xu
2017-08-22  1:58           ` Meng Xu
2017-08-21  8:38         ` Andrii Anisov
2017-08-22  2:19           ` Meng Xu
2017-07-05  7:33 ` 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=1499839981.7756.11.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=andrii_anisov@epam.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xumengpanda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).