From: "Simon Martin" <smartin@milliways.cl>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
josh.whitehead@dornerworks.com,
Nate Studer <nate.studer@dornerworks.com>,
Robbie VanVossen <robert.vanvossen@dornerworks.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: ARINC653
Date: Mon, 09 Dec 2013 23:08:12 +0000 [thread overview]
Message-ID: <em5e5a2a52-6b50-4967-a499-c79a50ece0a4@smartin-alien> (raw)
In-Reply-To: <1386624485.14872.10.camel@Abyss>
[-- Attachment #1.1.1: Type: text/plain, Size: 1419 bytes --]
Thanks Dario,
>> smartin@smartin-xen:~/projects/trio/xen/pv499$ sudo xl cpupool-list
>> Name CPUs Sched Active Domain count
>> Pool-0 3 credit y 1
>> pv499 1 arinc653 y 1
>>
>Ok, which pcpus are in each pool? In theory, it shouldn't matter, but,
>you know...
>
Pool-0 has pcpu 1, 2 and 3
pv499 has pcpu 0.
>> So unless I am doing something silly it looks like I will have to go
>> to RT-Xen to get better timings. For the moment I'm going to leave
>> this and go on to getting more of my operating system working.
>>
>Well, RT-Xen is a great project, but it's mostly, if not all, about
>scheduling. I mean, all they do is introducing two new schedulers (with
>a couple of operational mode in each), and that's it... There is
>nothing
>there being done for reducing latency or jitter.
Thanks for the pointer. As my tests have shown, changing the scheduler
does not really alter the behaviour.
>
>I think, we'd better off (as soon as, as you said, you have more pieces
>in place), trying to figure out what is causing the behavior you're
>seeing and workaround/fix/amend it!
I agree.
>
>It's a busy period, with the 4.4 release, etc., but, as repeatedly
>said,
>I'm up for helping with this, if help is needed!
Thanks. This is something that is going to take a while to get sorted so
I'll definitely be plugging until way after 4.4 is done and dusted.
Regards.
>
[-- Attachment #1.1.2: Type: text/html, Size: 3288 bytes --]
[-- Attachment #1.2: Type: image/png, Size: 680 bytes --]
[-- Attachment #1.3: Type: image/png, Size: 680 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-12-09 23:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528A34C9.7010208@dornerworks.com>
2013-12-03 12:07 ` ARINC653 Simon Martin
2013-12-03 15:32 ` ARINC653 Nate Studer
2013-12-03 20:19 ` ARINC653 Simon Martin
2013-12-09 20:23 ` ARINC653 Simon Martin
2013-12-09 21:28 ` ARINC653 Dario Faggioli
2013-12-09 23:08 ` Simon Martin [this message]
2013-12-10 9:36 ` ARINC653 Dario Faggioli
2013-12-10 11:55 ` ARINC653 Simon Martin
2013-11-28 13:07 ARINC653 Simon Martin
2013-11-28 13:55 ` ARINC653 Simon Martin
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=em5e5a2a52-6b50-4967-a499-c79a50ece0a4@smartin-alien \
--to=smartin@milliways.cl \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=josh.whitehead@dornerworks.com \
--cc=nate.studer@dornerworks.com \
--cc=robert.vanvossen@dornerworks.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 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).