From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Development list for the linux-yocto*.git Linux kernel
repositories" <linux-yocto@yoctoproject.org>
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com
Subject: Re: [linux-yocto] [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
Date: Sun, 17 Mar 2013 00:04:06 -0400 [thread overview]
Message-ID: <514540B6.2090307@windriver.com> (raw)
In-Reply-To: <cover.1363428594.git.insop.song@gmail.com>
On 13-03-16 6:16 AM, Insop Song wrote:
> meta-realtime layer for testing sched_deadline and other real-time applications
>
> Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel
>
This looks good to me now, I still think we'll have some confusion
between the core "rt" images and core-image-realtime that we are
introducing here.
I may rename it core-image-realtime-extended as part of the merge,
if that's acceptable to you ? I think it will be something that
we'll need to revisit at some point, but that's not a good reason
to hold this back anymore.
I'll merge, do a quick test and push this out on Monday.
Cheers,
Bruce
> *applications tested are shown below:
>
> 1. rt-app
> - "rt-app" is a test application that starts multiple periodic threads
> in order to simulate a real-time periodic load
>
> - run example
>
> root@qemux86:~# rt-app -t 100000:35000:d -D 1
> [rt-app]<notice> [0] Using SCHED_DEADLINE policy:
> [rt-app]<notice> [0] starting thread with period: 100000, exec:
> 35000,deadline: 100000, priority: 10
> [rt-app]<notice> [0] Locking pages in memory
> idx period min_et max_et rel_st start end
> deadline dur. slack Budget Used Budget
> 0 100000 35000 35000 64705 305724113 305759126
> 305824105 35013 64979
> ...
> 0 100000 35000 35000 965099 306624507 306659526
> 306724105 35019 64578
> [rt-app]<notice> [0] Exiting.
>
> 2. schedtool
> - scheduler test tool
> - run example
> root@qemux86:~# schedtool -E -t 10000:100000 -a 0 -e yes> /dev/null&
> root@qemux86:~# schedtool -E -t 30000:100000 -a 0 -e yes> /dev/null&
> root@qemux86:~# jobs
> [1]- Running schedtool -E -t 10000:100000 -a 0 -e yes
> > /dev/null&
> [2]+ Running schedtool -E -t 30000:100000 -a 0 -e yes
> > /dev/null&
>
> $ top
> Mem: 33616K used, 84308K free, 0K shrd, 2684K buff, 13904K cached
> CPU: 37% usr 5% sys 0% nic 56% idle 0% io 0% irq 0% sirq
> Load average: 911.65 428.84 84.32 35501/62 715
> PID PPID USER STAT VSZ %VSZ %CPU COMMAND
> 714 688 root R 2352 2% 28% yes
> 713 688 root R 2352 2% 9% yes
> 715 688 root R 2724 2% 4% top
>
> Insop Song (1):
> Add rt-app, schedtool, define core-image-realtime, and append
> recipies-kernel
>
> recipes-extended/images/core-image-realtime.bb | 12 +++++++++
> recipes-kernel/linux/linux-yocto_3.8.bbappend | 9 +++++++
> ...adline-as-a-default-to-go-around-yocto-bu.patch | 26 ++++++++++++++++++
> recipes-tools/rt-app/rt-app.bb | 28 ++++++++++++++++++++
> recipes-tools/schedtool-dl/schedtool-dl.bb | 23 ++++++++++++++++
> 5 files changed, 98 insertions(+)
> create mode 100644 recipes-extended/images/core-image-realtime.bb
> create mode 100644 recipes-kernel/linux/linux-yocto_3.8.bbappend
> create mode 100644 recipes-tools/rt-app/files/0001-set-with-deadline-as-a-default-to-go-around-yocto-bu.patch
> create mode 100644 recipes-tools/rt-app/rt-app.bb
> create mode 100644 recipes-tools/schedtool-dl/schedtool-dl.bb
>
next prev parent reply other threads:[~2013-03-17 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <insop.song@gmail.com>
2013-03-16 10:16 ` [PATCH 0/1] [meta-realtime] Add rt-app, schedtool, define core-image-realtime, and append recipies-kernel Insop Song
2013-03-16 10:16 ` [PATCH 1/1] " Insop Song
2013-03-17 4:04 ` Bruce Ashfield [this message]
2013-03-17 7:36 ` [linux-yocto] [PATCH 0/1] " Insop Song
2013-03-18 14:21 ` Bruce Ashfield
2013-03-18 15:46 ` Insop Song
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=514540B6.2090307@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=linux-yocto@yoctoproject.org \
--cc=yocto@yoctoproject.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.