From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Insop Song <insop.song@gmail.com>
Cc: Juri Lelli <j.lelli@sssup.it>,
"Development list for the linux-yocto*.git Linux kernel
repositories" <linux-yocto@yoctoproject.org>,
yocto@yoctoproject.org
Subject: Re: A question on adding a new program to a new meta layer
Date: Thu, 7 Mar 2013 20:46:55 -0500 [thread overview]
Message-ID: <5139430F.40403@windriver.com> (raw)
In-Reply-To: <CACzyEJ_gBWMYyjcy2PaYuswviK4SoQn=W06vQet+LmOdjZBm1w@mail.gmail.com>
On 13-03-07 4:49 PM, Insop Song wrote:
>>
>> Thanks Juri, I was going to add you to my linux-yocto-3.8 announcement
>> email and due to some last minute debug activities .. it slipped my
>> mind. So I'm using this thread to let you, and anyone else that is
>> interested know that sched_deadline support is available to try out
>> in linux-yocto-3.8.
>>
>
> Could you also add me in the announcement list?
I can definitely do that.
Also if you sign up for the linux-yocto@yoctoproject.org
mailing list, that's where announcements and kernel feature discussions
happen around linux-yocto. It would be a great place (versus this
main yocto mailing list) to talk about sched_deadline in particular.
>
>>
>>>
>>> As I already told to Insop, I don't have any automated test for the
>>> patchset, but I usually run different scenarios using basically this
>>> two tools (and giving a look at simple cases through kernelshark):
>>>
>>> 1- schedtool-dl: https://github.com/jlelli/schedtool-dl
>>> the idea here is to let a 'yes' run through SCHED_DEADLINE and
>>> check through kernelshark that the bandwidth enforcement
>>> mechanism works.
>>>
>>> 2- rt-app: https://github.com/gbagnoli/rt-app
>>> with this I usually let some tasksets run for several hours on
>>> a 48-cores machine we have in our lab, I can provide the tasksets
>>> (json files) and the script to run them.
>>>
>>> Please let me know how I can help further.
>>
>>
>> This is a good start. I have some old references to tests that I'll
>> dig up as well.
>>
>
> You can check this recipes-tool to find out the above programs
> (configuration and installation) in here,
> https://github.com/insop/meta-dl/tree/sched-dl-V7/recipes-tools
>
>
>> I'm looking to develop some "real world" examples of the scheduler
>> class in action, since as we've been saying .. getting those examples
>> will both help the approach and perhaps help get it merged into the
>> mainline kernel.
>>
>
> I've been looking application descriptions when I was in Ericsson, and
> provided cases to Thomas and Juri.
> I am interested in this as well, and include them in easy-to test/validate form.
Great!
Bruce
>
> I will also reply to your other mail shortly.
>
> Regards,
>
> Insop
next prev parent reply other threads:[~2013-03-08 1:47 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACzyEJ_3BRjn4s7ADey9uuQpGhgWKeuuyxGVL09HuLAzJ3LqTQ@mail.gmail.com>
2013-03-05 6:54 ` A question on adding a new program to a new meta layer Insop Song
2013-03-07 4:00 ` Bruce Ashfield
2013-03-07 4:24 ` Juri Lelli
2013-03-07 13:53 ` Bruce Ashfield
2013-03-07 21:49 ` Insop Song
2013-03-08 1:46 ` Bruce Ashfield [this message]
2013-03-08 4:12 ` Insop Song
2013-03-07 5:05 ` Insop Song
2013-03-07 8:26 ` Insop Song
2013-03-07 14:05 ` Bruce Ashfield
2013-03-07 22:02 ` Insop Song
2013-03-08 1:47 ` Bruce Ashfield
2013-03-08 11:10 ` Insop Song
2013-03-07 14:04 ` Bruce Ashfield
2013-03-08 13:27 ` Insop Song
2013-03-08 16:32 ` Bruce Ashfield
2013-03-08 17:03 ` Darren Hart
2013-03-08 17:36 ` Bruce Ashfield
2013-03-07 14:08 ` Bruce Ashfield
2013-03-07 21:43 ` Insop Song
2013-03-08 1:45 ` Bruce Ashfield
2013-03-08 4:02 ` Juri Lelli
2013-03-05 9:19 ` Insop Song
2013-03-08 17:01 ` Darren Hart
2013-03-08 23:35 ` Bruce Ashfield
2013-03-09 10:32 ` Insop Song
2013-03-11 3:28 ` Bruce Ashfield
2013-03-11 3:32 ` Insop Song
2013-03-11 14:34 ` Bruce Ashfield
2013-03-11 16:07 ` Insop Song
2013-03-11 17:03 ` Bruce Ashfield
2013-03-11 17:20 ` 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=5139430F.40403@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=insop.song@gmail.com \
--cc=j.lelli@sssup.it \
--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.