xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrii Anisov <andrii_anisov@epam.com>
To: Meng Xu <mengxu@cis.upenn.edu>, dario.faggioli@citrix.com
Cc: xumengpanda@gmail.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 0/5] Towards work-conserving RTDS
Date: Mon, 2 Oct 2017 17:38:11 +0300	[thread overview]
Message-ID: <ec27fb70-9f61-3e15-1db5-f3fa1760873b@epam.com> (raw)
In-Reply-To: <1504281532-3766-1-git-send-email-mengxu@cis.upenn.edu>

Hello Meng Xu and Dario,

On 01.09.17 18:58, Meng Xu wrote:
> This series of patches make RTDS scheduler work-conserving
> without breaking real-time guarantees.
> VCPUs with extratime flag set can get extra time
> from the unreserved system resource.
> System administrators can decide which VCPUs have extratime flag set.
As I understand from threads and the code, the work conserving algorithm 
is quite simplistic and will prefer a vcpu with greater utilization.

 From our side we are looking for a bit different solution. I.e., in the 
same cpupool, running vcpus eager for RT characteristics under EDF 
conditions, and share the rest of resources between non-rt vcpus (i.e. 
in a credit manner).
Possible use-case could be a system with a domain hunger for resources, 
but not critical (some infotainment system) and an RT domain utilizing 
at most 20% of a single CPU core. Having a SoC with 4 cores, 
partitioning would be a significant resources wasting for described 
scenario.

How feasible is it from your point of view?

BTW, are you targeting XEN 4.10 with this patch series?

-- 

*Andrii Anisov*



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  parent reply	other threads:[~2017-10-02 14:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01 15:58 [PATCH v2 0/5] Towards work-conserving RTDS Meng Xu
2017-09-01 15:58 ` [PATCH v2 1/5] xen:rtds: towards work conserving RTDS Meng Xu
2017-09-14  1:06   ` Dario Faggioli
2017-09-15 15:38     ` Meng Xu
2017-09-01 15:58 ` [PATCH v2 2/5] libxl: enable per-VCPU extratime flag for RTDS Meng Xu
2017-09-01 16:03   ` Meng Xu
2017-09-14  0:16     ` Dario Faggioli
2017-09-15 16:01       ` Meng Xu
2017-09-19  9:23         ` Dario Faggioli
2017-10-09 16:08           ` Meng Xu
2017-09-14  0:12   ` Dario Faggioli
2017-09-01 15:58 ` [PATCH v2 3/5] xl: " Meng Xu
2017-09-14  0:51   ` Dario Faggioli
2017-10-09 16:13     ` Meng Xu
2017-10-09 17:19       ` Dario Faggioli
2017-09-14  0:58   ` Dario Faggioli
2017-09-01 15:58 ` [PATCH v2 4/5] xentrace: " Meng Xu
2017-09-14  0:55   ` Dario Faggioli
2017-09-01 15:58 ` [PATCH v2 5/5] docs: " Meng Xu
2017-09-14  0:59   ` Dario Faggioli
2017-09-13 10:28 ` [PATCH v2 0/5] Towards work-conserving RTDS Wei Liu
2017-09-13 10:42   ` Dario Faggioli
2017-10-02 14:38 ` Andrii Anisov [this message]
2017-10-02 17:04   ` Dario Faggioli
2017-10-02 19:18     ` Meng Xu

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=ec27fb70-9f61-3e15-1db5-f3fa1760873b@epam.com \
    --to=andrii_anisov@epam.com \
    --cc=dario.faggioli@citrix.com \
    --cc=mengxu@cis.upenn.edu \
    --cc=xen-devel@lists.xen.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).