Hi Stephen,
(replying to really old post, sorry)
On 02/10/15 08:06, Stephen Flowers wrote:
I have built the realtime kernel using Yocto and deployed on the
beaglebone black (specifically core-image-rt-sdk).
I'm curious to know how you built your image. When I try bitbake
core-image-rt or
Trevor,
I added the following to .../build/conf/local.conf
PREFERRED_PROVIDER_virtual/kernel = linux-yocto-rt
COMPATIBLE_MACHINE_beaglebone = beaglebone
COMPATIBLE_MACHINE_quilt-native = beaglebone
Then change the required package within
/meta/recipes-rt/images/core-image-rt.bb from -minimal
On 15-02-18 10:19 AM, Stephen Flowers wrote:
The device is just a gpio pin registered at /sys/class/gpio/gpioxx/value
Can you link to where I can read about the well known latency issues
running -rt with USB and flash? The rootfs is located on flash so could
this explain the cause?
I should
On 15-02-17 05:57 PM, Stephen Flowers wrote:
I loaded the system effectively and also changed my rt application to
use asynchronous IO - I find the rt kernel is much tighter at periodic
latency yet seems to be worse in the latency measurements. I'm asuming
the non-deteministic nature of
The device is just a gpio pin registered at /sys/class/gpio/gpioxx/value
Can you link to where I can read about the well known latency issues
running -rt with USB and flash? The rootfs is located on flash so could
this explain the cause?
Steve
On 18/02/2015 14:57, Bruce Ashfield wrote:
On
I loaded the system effectively and also changed my rt application to
use asynchronous IO - I find the rt kernel is much tighter at periodic
latency yet seems to be worse in the latency measurements. I'm asuming
the non-deteministic nature of userland file IO operations is causing
the
On 02/12/2015 05:05 PM, Stephen Flowers wrote:
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero /dev/null
When I suggested filesystem activity I was suggesting getting a kernel
filesystem and a physical I/O device to be active.
The load above is
On 2015-02-12 7:20 PM, William Mills wrote:
On 02/12/2015 05:05 PM, Stephen Flowers wrote:
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero /dev/null
When I suggested filesystem activity I was suggesting getting a kernel
filesystem and a
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero /dev/null
#cyclictest -a 0 -p 99 -m -n -l 10 -q
I ran this command as shown by Toyoka at the 2014 Linuxcon Japan
+ meta-ti
Please keep meta-ti in the loop.
[Sorry for the shorting. Thunderbird keep locking up when I tried
replay all in plain text to this message.]
~ 15-02-11, Stephen Flowers wrote:
Thanks for your input. Here are results of 1000 samples over a
10 second period:
Interrupt response
On 2015-02-11 7:35 PM, William Mills wrote:
+ meta-ti
Please keep meta-ti in the loop.
[Sorry for the shorting. Thunderbird keep locking up when I tried
replay all in plain text to this message.]
Heh. I know the pain, the giant .configs can give it a fit.
~ 15-02-11, Stephen Flowers
Thanks for your input. Here are results of 1000 samples over a 10
second period:
Interrupt response (microseconds)
standard: min: 81, max:118, average: 84
rt: min: 224, max: 289, average: 231
Will share the .config later once I get on that machine.
Steve
On 10/02/2015 14:16, Bruce
On 15-02-10 09:39 AM, Stephen Flowers wrote:
Thanks for your input. Here are results of 1000 samples over a 10
second period:
To be clear ? Is that the cyclictest run that I was asking
about ?
If it is, what parameters did you use for the run ? It makes a
huge difference in the results from
Sorry, no I have not run cyclictest yet. The results are latencies
measured via gpio toggles from running the code posted previously.
Steve
On 10/02/2015 14:40, Bruce Ashfield wrote:
On 15-02-10 09:39 AM, Stephen Flowers wrote:
Thanks for your input. Here are results of 1000 samples over
Hi All,
I have built the realtime kernel using Yocto and deployed on the
beaglebone black (specifically core-image-rt-sdk). I have written a
program to test the timer latency and interrupt latency of userspace
applications. For this I'm using a simple timerfd to generate a
periodic 10ms
On 15-02-10 08:06 AM, Stephen Flowers wrote:
Hi All,
I have built the realtime kernel using Yocto and deployed on the
beaglebone black (specifically core-image-rt-sdk). I have written a
program to test the timer latency and interrupt latency of userspace
applications. For this I'm using a
16 matches
Mail list logo
