rtems_iterate_over_all_threads

[Thomas Dörfler]

Leon,

wouldn't it be better in that case to reaise your own priority beyond
all other tasks? This would make sure your task has the processor on its
own until it blocks (e.g. in an I/O operation).

When you suspend a bunch of tasks, you might even have to track, which
tasks already where suspended, to avoid that you resume a task that was
suspended by another piece of code...

wkr,
Thomas.

Leon Pollak wrote:
> Hello, all.
> 
> I was glad to find the new rtems_iterate_over_all_threads API function - a 
> useful thing in my case. What I want is to suspend temporary all tasks (except 
> this which issues this command) and then, later, may be resume them.
> 
> Great! But then I found a real obstacle to do this - to avoid myself 
> suspension I need to compare myself ID with the "current" ID. For this, in 
> turn, I need to use rtems_task_ident... Too complex and time consuming!
> 
> Will not it be better to add a parameter to rtems_iterate_over_all_threads 
> saying to avoid myself ID while iterating?
> 
> Thanks.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.com
> http://rtems.rtems.org/mailman/listinfo/rtems-users


-- 
--------------------------------------------
IMD Ingenieurbuero fuer Microcomputertechnik
Thomas Doerfler           Herbststrasse 8
D-82178 Puchheim          Germany
email:    Thomas.Doerfler at imd-systems.de
PGP public key available at:
     http://www.imd-systems.de/pgpkey_en.html