On Oct 29, 2010, at 8:25 AM, Andrew Johnson wrote:
>>
>
> Actually it doesn't look that bad, just that the test code isn't waiting long
> enough for all the once-<n> threads to run; they are running later on, but by
> then it's stopped counting. Try increasing the delay immediately before the
> testOk(doneCount==...) line.
>
> This is the place where I really wanted a broadcast epicsEvent that would
> start all the waiting threads at once, to test that the once really can't be
> executed in parallel.
>
For strict priority-based systems would it not be possible to get this effect by starting all the threads at a lower priority than the main thread -- then when the main thread pauses all the others get to fight for the CPU?
--
Eric Norum
[email protected]
- Replies:
- Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- References:
- Re: epicsEvent Eric Norum
- RTEMS tests -- epicsThreadOnce broken? Eric Norum
- Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- Navigate by Date:
- Prev:
Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- Next:
Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- Next:
Re: RTEMS tests -- epicsThreadOnce broken? Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|