All of lore.kernel.org
 help / color / mirror / Atom feed
From: Meng Xu <xumengpanda@gmail.com>
To: Andrii Anisov <andrii_anisov@epam.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Dario Faggioli <dfaggioli@suse.com>
Subject: Re: RTDS with extra time issue
Date: Fri, 9 Feb 2018 12:53:37 -0500	[thread overview]
Message-ID: <CAENZ-+kdiGJe9UT8fP-w=T2GzTDm5AQr5zgdMLFUAsKsAFLQiQ@mail.gmail.com> (raw)
In-Reply-To: <a3d0cbcf-2bee-391f-39de-d19906616fc6@epam.com>

[-- Attachment #1: Type: text/plain, Size: 558 bytes --]

On Fri, Feb 9, 2018 at 11:04 AM, Andrii Anisov <andrii_anisov@epam.com> wrote:
>
> On 09.02.18 17:34, Meng Xu wrote:
>>
>> If you want to keep the same VCPU parameter, can you try to set task's
>> period = 100ms and exe time = 40ms?
>> By theory (I used CARTS to compute), a VCPU (10ms, 5ms) can schedule a
>> task (100ms, 40ms).
>> Note that the resource demand of two RT tasks with the same utilization is
>> different: the task with smaller period has larger demand.
>
> BTW, could you please share the model xml file to me?
>

Sure!
It's attached.

Meng

[-- Attachment #2: example-in.xml --]
[-- Type: text/xml, Size: 178 bytes --]

<system os_scheduler="EDF" period="2"> 
	<component name="C0" scheduler="EDF" period="10"> 
		 <task name="T0" p="100" d="100" e="40" > </task>
		 
	</component>
</system>

[-- Attachment #3: example-out.xml --]
[-- Type: text/xml, Size: 508 bytes --]

<component name="OS Scheduler" algorithm="PRM interface">
	<resource>
		<model period="2" bandwidth="1" deadline="2"> </model>
	</resource>
	<processed_task>
		<model period="2" execution_time="2" deadline="2"> </model>
	</processed_task>
	<component name="C0" algorithm="PRM interface">
		<resource>
			<model period="10" bandwidth="0.5" deadline="10"> </model>
		</resource>
		<processed_task>
			<model period="10" execution_time="5" deadline="10"> </model>
		</processed_task>
	</component>
</component>

[-- Attachment #4: Type: text/plain, Size: 157 bytes --]

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

  reply	other threads:[~2018-02-09 17:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 12:20 RTDS with extra time issue Andrii Anisov
2018-02-09 12:25 ` Andrii Anisov
2018-02-09 13:18 ` Dario Faggioli
2018-02-09 15:03   ` Andrii Anisov
2018-02-09 15:18     ` Dario Faggioli
2018-02-09 15:36       ` Meng Xu
2018-02-09 15:56         ` Andrii Anisov
2018-02-09 17:51           ` Meng Xu
2018-02-10  0:14             ` Dario Faggioli
2018-02-10  4:53               ` Meng Xu
2018-02-12 10:17                 ` Dario Faggioli
2018-02-12 11:08                   ` Andrii Anisov
2018-02-12 14:52                     ` Meng Xu
2018-02-12 10:38                 ` Andrii Anisov
2018-02-12 10:20       ` Andrii Anisov
2018-02-12 18:44         ` Andrii Anisov
2018-02-16 18:37           ` Dario Faggioli
2018-02-20 11:34             ` Andrii Anisov
2018-02-22 17:53               ` Dario Faggioli
2018-02-26 12:00                 ` Andrii Anisov
2018-02-09 15:34 ` Meng Xu
2018-02-09 15:53   ` Andrii Anisov
2018-02-09 16:04   ` Andrii Anisov
2018-02-09 17:53     ` Meng Xu [this message]
2018-02-09 18:07       ` Andrii Anisov

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='CAENZ-+kdiGJe9UT8fP-w=T2GzTDm5AQr5zgdMLFUAsKsAFLQiQ@mail.gmail.com' \
    --to=xumengpanda@gmail.com \
    --cc=andrii_anisov@epam.com \
    --cc=dfaggioli@suse.com \
    --cc=xen-devel@lists.xenproject.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.