Hi Andrii,
I'm sorry for replying to this thread late. I was busy with a paper
deadline until last Saturday morning.
I saw Dario's thorough answer which explains the high-level idea of
the real-time analysis that is the theoretical foundation of the
analysis tool, e.g., CARTs.
Hopefully, he answe
Hello Dario,
On 28.09.17 19:01, Dario Faggioli wrote:
On Thu, 2017-09-28 at 12:18 +0300, Andrii Anisov wrote:
- Could you please provide an example input xml for CARTS
described a
system with 2 RT domains with 2 VCPUs each, running on a 2PCPUs,
with gEDF
scheduling at VMM level (for XEN
On Thu, 2017-09-28 at 18:01 +0200, Dario Faggioli wrote:
> On Thu, 2017-09-28 at 12:18 +0300, Andrii Anisov wrote:
> > > >
> The GP scheduler --like Credit1 or Credit2, if you are on Xen-- will
> give you fairness, but without any precise temporal guarantee. This
> means that, in this case, each v
On Thu, 2017-09-28 at 12:18 +0300, Andrii Anisov wrote:
> > > - Could you please provide an example input xml for CARTS
> > > described a
> > > system with 2 RT domains with 2 VCPUs each, running on a 2PCPUs,
> > > with gEDF
> > > scheduling at VMM level (for XEN based setup).
> >
> > Hmm, if
Hello,
On 27.09.17 22:57, Meng Xu wrote:
Note that:
When you use gEDF scheduler in VM or VMM (i.e., Xen), you should use
MPR2 model
I guess you mean DMPR in CARTS terms.
to compute the resource interface (i.e., VCPU parameters).
When you use pEDF scheduler, you should use PRM model to comp
On Wed, Sep 27, 2017 at 10:37 AM, Andrii Anisov wrote:
> Hello,
>
>
> On 27.09.17 16:57, Meng Xu wrote:
>>
>> The command is:
>> java -jar carts.jar inputfile outputfile
>
> From the next example, I would say the command is:
> java -jar carts.jar inputfile interface_type outputfile
>
>> An exa
Hello,
On 27.09.17 16:57, Meng Xu wrote:
The command is:
java -jar carts.jar inputfile outputfile
From the next example, I would say the command is:
java -jar carts.jar inputfile interface_type outputfile
An example command is:
java -jar carts.jar 1-1.10-in.xml MPR2 1-1.10-out.xml
Thank
Hi Andrii,
On Wed, Sep 27, 2017 at 8:37 AM, Andrii Anisov wrote:
>
> Dear Meng Xu,
>
>
> On 22.08.17 05:02, Meng Xu wrote:
>>
>> Given the set of tasks in each VM, we compute the VCPUs' periods and
>> budgets, using the CARTS tool [1]. Note that each task has a period
>> and a worst-case executio
Dear Meng Xu,
On 22.08.17 05:02, Meng Xu wrote:
Given the set of tasks in each VM, we compute the VCPUs' periods and
budgets, using the CARTS tool [1]. Note that each task has a period
and a worst-case execution time (wcet).
[1] https://rtg.cis.upenn.edu/carts/
In a CARTS tool documentation
On Mon, Aug 21, 2017 at 4:38 AM, Andrii Anisov wrote:
>
> On 18.08.17 23:43, Meng Xu wrote:
>>
>> Sure. The workload we used in the paper is mainly the cpu-intensive task.
>> We first calibrate a busy-loop of multiplications that runs for 1ms.
>> Then for a task that executes for exe(ms), we simpl
On Mon, Aug 21, 2017 at 4:16 AM, Andrii Anisov wrote:
>
> On 21.08.17 11:07, Andrii Anisov wrote:
>>
>> Hello Meng Xu,
>>
>>
>> On 18.08.17 23:43, Meng Xu wrote:
>>>
>>> The Section 4.1 and 4.2 in [1] explained the whole experiment steps.
>>> If you have any question or confusion on a specific ste
On Mon, Aug 21, 2017 at 4:07 AM, Andrii Anisov wrote:
>
> Hello Meng Xu,
>
>
> On 18.08.17 23:43, Meng Xu wrote:
>>
>> The Section 4.1 and 4.2 in [1] explained the whole experiment steps.
>> If you have any question or confusion on a specific step, please feel
>> free to let me know.
>
> From the
On 18.08.17 23:43, Meng Xu wrote:
Sure. The workload we used in the paper is mainly the cpu-intensive task.
We first calibrate a busy-loop of multiplications that runs for 1ms.
Then for a task that executes for exe(ms), we simply let the task
execute the 1ms busy loop for exe times.
I'm a bit co
On 21.08.17 11:07, Andrii Anisov wrote:
Hello Meng Xu,
On 18.08.17 23:43, Meng Xu wrote:
The Section 4.1 and 4.2 in [1] explained the whole experiment steps.
If you have any question or confusion on a specific step, please feel
free to let me know.
From the document it is not really clear if
Hello Meng Xu,
On 18.08.17 23:43, Meng Xu wrote:
The Section 4.1 and 4.2 in [1] explained the whole experiment steps.
If you have any question or confusion on a specific step, please feel
free to let me know.
From the document it is not really clear if you ran one guest RT domain
or several si
Hi Andrii,
On Tue, Aug 1, 2017 at 4:02 AM, Andrii Anisov wrote:
> Hello Meng Xu,
>
> I've get back to this stuff.
Sorry for the late response. I'm not sure if you have already solved this.
>
>
> On 03.07.17 17:58, Andrii Anisov wrote:
>>
>> That's why we are going to keep configuration (of gues
Hello Meng Xu,
I've get back to this stuff.
On 03.07.17 17:58, Andrii Anisov wrote:
That's why we are going to keep configuration (of guests and
workloads) close to [1] for evaluation, but on our target SoC.
I'm wondering if there are known issues or specifics for ARM.
[1] https://www.cis.up
On Fri, 2017-07-07 at 14:29 -0400, Meng Xu wrote:
> On Wed, Jul 5, 2017 at 4:29 AM, Dario Faggioli
> 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
Hello Meng Xu,
On 07.07.17 21:43, Meng Xu wrote:
Andrii,
If you encountered any question/difficulty in choosing the proper VCPU
parameters for your workload, please don't hesitate to ping me and
Dario.
Thank you. I'll keep you in touch when we have something specified.
--
*Andrii Anisov*
_
[sorry, my finger slips. let me rephrase my last sentence.]
>
>> For example, if you have a particular task in the VM that you need must
>> absolutely execute for at least 10ms every 100ms, you can:
>> - inside the VM, pin the task to vCPU 0, and give it top priority;
>> - at the Xen level, give (
On Wed, Jul 5, 2017 at 4:51 AM, Dario Faggioli
wrote:
> On Mon, 2017-07-03 at 14:42 -0400, Meng Xu wrote:
>> On Mon, Jul 3, 2017 at 10:58 AM, Andrii Anisov > m> wrote:
>> >
>> Once the scheduling policy is determined, you will need to configure
>> the VCPUs' parameters based on the systems' worklo
On Wed, Jul 5, 2017 at 4:29 AM, Dario Faggioli
wrote:
> On Tue, 2017-07-04 at 11:12 -0400, Meng Xu wrote:
>> On Tue, Jul 4, 2017 at 8:28 AM, Andrii Anisov > > wrote:
>> >
>> > So you are suggesting to introduce more RT schedulers with
>> > different algorithms. Did I get you right?
>>
>> The EDF s
On Mon, 2017-07-03 at 14:42 -0400, Meng Xu wrote:
> On Mon, Jul 3, 2017 at 10:58 AM, Andrii Anisov m> wrote:
> >
> Once the scheduling policy is determined, you will need to configure
> the VCPUs' parameters based on the systems' workload.
> This requires the workload's timing parameters for the
On Tue, 2017-07-04 at 15:28 +0300, Andrii Anisov wrote:
> On 03.07.17 21:42, Meng Xu wrote:
> >
> > The RTDS uses the EDF scheduling, under which the priorities of the
> > VCPUs (or VMs) are dynamically changed based on their (absolute)
> > deadlines. This provides better real-time performance for
On Tue, 2017-07-04 at 11:12 -0400, Meng Xu wrote:
> On Tue, Jul 4, 2017 at 8:28 AM, Andrii Anisov > wrote:
> >
> > So you are suggesting to introduce more RT schedulers with
> > different algorithms. Did I get you right?
>
> The EDF scheduling cares about the overall system's RT performance.
> I
On Mon, 2017-07-03 at 14:03 +0300, Andrii Anisov wrote:
> - root@salvator-x-h3-xt:/scripts# xl sched-rtds -d DomU -v all -p
> 1
> -b 2500
> (XEN) FLASK: Denying unknown domctl_scheduler_op: 2.
> libxl: error: libxl_sched.c:663:sched_rtds_vcpu_set_all: Domain
> 2:Setting vcpu sched rtds:
On Tue, Jul 4, 2017 at 8:28 AM, Andrii Anisov wrote:
>
>
> On 03.07.17 21:42, Meng Xu wrote:
>>
>> As far as I know, there is no known issue for ARM as long as that
>> version Xen runs on the ARM board.
>
> That's good.
>>
>> I assume you have your own workloads to run, which are periodically
>>
On 03.07.17 21:42, Meng Xu wrote:
As far as I know, there is no known issue for ARM as long as that
version Xen runs on the ARM board.
That's good.
I assume you have your own workloads to run, which are periodically
activated task.
The workloads in [1] are independent periodic CPU-intensive t
On Mon, Jul 3, 2017 at 10:58 AM, Andrii Anisov wrote:
> Hello Meng Xu,
>
>
> On 03.07.17 16:35, Meng Xu wrote:
>>>
>>> Do you have any recommendations or suggestions?
>>
>> Which experiment/use case do you plan to run?
>> What are the requirements (or performance guarantees) you want to have
>> fr
Hello Meng Xu,
On 03.07.17 16:35, Meng Xu wrote:
Do you have any recommendations or suggestions?
Which experiment/use case do you plan to run?
What are the requirements (or performance guarantees) you want to have
from RTDS?
Currently we have no defined target use-cases.
That's why we are goi
On Mon, Jul 3, 2017 at 7:03 AM, Andrii Anisov wrote:
>
> Dear Meng Xu,
Hi Andrii,
>
>
> We are going to evaluate an RTDS scheduler on ARM.
>
>
> Basically I'm going to repeat use-cases described in
> https://www.cis.upenn.edu/~linhphan/papers/emsoft14-rt-xen.pdf in some amount.
I see. Please
On 03.07.17 16:03, Wei Liu wrote:
This is a bit strange, fc658208e026242420b9924a9e4bfa581479e1f5 seems to
imply xentop should work on ARM.
Yep it is built.
But yocto missed its installation. That issue is on our site :)
--
*Andrii Anisov*
___
Xe
On Mon, Jul 03, 2017 at 02:03:33PM +0300, Andrii Anisov wrote:
> Dear Meng Xu,
>
> We are going to evaluate an RTDS scheduler on ARM.
>
> Basically I'm going to repeat use-cases described in
> https://www.cis.upenn.edu/~linhphan/papers/emsoft14-rt-xen.pdf in some
> amount.
>
> Do you have any re
Dear Meng Xu,
We are going to evaluate an RTDS scheduler on ARM.
Basically I'm going to repeat use-cases described in
https://www.cis.upenn.edu/~linhphan/papers/emsoft14-rt-xen.pdf in some
amount.
Do you have any recommendations or suggestions?
BTW, even following
https://xenbits.xen.org/
34 matches
Mail list logo
