[Tinyos Core WG] TOSThreads TEP

[Kevin Klues]

Again, the motivation behind the dynamic threads was for emabling
dynamically loadable binaries at runtime.  This way you can have a
mote sitting out in the field with a 'kernel' on it, and you can ship
it a thread based binary that it can link and load at runtime.

kevin

On Tue, May 20, 2008 at 4:15 PM, Miklos Maroti <mmaroti at math.u-szeged.hu> wrote:
>> Of course, function pointers wouldn't be necessary if we
>> supported only Static threads (using terminology borrowed from the
>> TEP), to allow flexibility in the definition and use of dynamic
>> threads, function pointers are necessary.
>
> To be frank, I would not allow dynamic threads at all because of the
> following simple reasons:
>
> - Why would threads be any different from memory allocation, we have
> static memory allocation, static composition, etc.
>
> - You cannot do whole application analysis (included WC stack usage)
> if you have dynamic threads.
>
> - Janos Sallai has a tool (documented in his thesis) that can compile
> away static threads into normal tinyos event driven code. Keeping the
> threads static allows other people to implement threading in a
> completely different way: competition is good (TM).
>
> Miklos
>



-- 
~Kevin