boost.tasklet is a split-up from old boost.fiber. The lib allow to execute micro-tasks (tasklets) in a thread and assigns each small task with a micro-thread/fiber - so tasklets are cooperativly scheduled. The API contains classes and functions to manage and synchronize tasklets (even if the tasklets are running on different threads). boost.tasklet is an example how boost.fiber could be used for cooperative scheduling ansd will be used by the threadpool from boost.task. Oliver
2011/1/9 Oliver Kowalke <k-oli@gmx.de>:
boost.tasklet is a split-up from old boost.fiber. The lib allow to execute micro-tasks (tasklets) in a thread and assigns each small task with a micro-thread/fiber - so tasklets are cooperativly scheduled. The API contains classes and functions to manage and synchronize tasklets (even if the tasklets are running on different threads). boost.tasklet is an example how boost.fiber could be used for cooperative scheduling ansd will be used by the threadpool from boost.task.
Which is the different between tasklets and coroutines?
Oliver _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Quiero ser el rayo de sol que cada día te despierta para hacerte respirar y vivir en me. "Favola -Moda".
As I wrote in the docu a tasklet is associated with a fiber. The difference between a fiber and a coroutine is that the coroutine can be seen as a language-level construct while a fiber is a system-level construct (fibers are conceptualy equivalent to coroutines). boost.tasklet provides an scheduler interface and comes with a round-robin scheduler (priority scheduler is planed). Am 09.01.2011 16:56, schrieb Giorgio Zoppi:
2011/1/9 Oliver Kowalke<k-oli@gmx.de>:
boost.tasklet is a split-up from old boost.fiber. The lib allow to execute micro-tasks (tasklets) in a thread and assigns each small task with a micro-thread/fiber - so tasklets are cooperativly scheduled. The API contains classes and functions to manage and synchronize tasklets (even if the tasklets are running on different threads). boost.tasklet is an example how boost.fiber could be used for cooperative scheduling ansd will be used by the threadpool from boost.task.
Which is the different between tasklets and coroutines?
Oliver
Additional notes: boost.tasklet comes with some class for syncing tasklets. For instance event and conmdition variables, channels (messages exchange) and mutexes etc. AFAIK such facilities are uncommon with coroutines. Am 09.01.2011 16:56, schrieb Giorgio Zoppi:
2011/1/9 Oliver Kowalke<k-oli@gmx.de>:
boost.tasklet is a split-up from old boost.fiber. The lib allow to execute micro-tasks (tasklets) in a thread and assigns each small task with a micro-thread/fiber - so tasklets are cooperativly scheduled. The API contains classes and functions to manage and synchronize tasklets (even if the tasklets are running on different threads). boost.tasklet is an example how boost.fiber could be used for cooperative scheduling ansd will be used by the threadpool from boost.task.
Which is the different between tasklets and coroutines?
Oliver _______________________________________________ Unsubscribe& other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
participants (2)
-
Giorgio Zoppi -
Oliver Kowalke