Slicer3:ThreadingToolKit - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T18:07:19Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Marianna: Unprotected "Slicer3:ThreadingToolKit"

2008-05-20T17:51:41Z

Unprotected "Slicer3:ThreadingToolKit"

Marianna at 17:51, 20 May 2008

2008-05-20T17:51:26Z

Aylward at 15:32, 3 August 2007

2007-08-03T15:32:20Z

Blezek at 12:48, 3 August 2007

2007-08-03T12:48:33Z

New page

=== Purpose ===

Just as the [[Slicer3:Execution_Model| Execution Model]] has enabled algorithm developers to rapidly integrate their software into Slicer3, the purpose of the Threading ToolKit (TTK) is to enable algorithm and application developers to easily take advantage of multi core threaded environments.

=== Goals ===

* Provide building blocks inspired by [http://www.openmp.org OpenMP], [http://java.sun.com/docs/books/tutorial/essential/concurrency/index.html Java's concurrency model], and [http://osstbb.intel.com/ Intel's Threading Building Blocks].
* Provide a cross platform C++ implementation for
** POSIX pthreads
** Windows threading
** Single threaded implementation
* Attempt a header only implementation, to minimize developer overhead

=== Design thoughts ===

==== Thread Pool ====
Provide a thread pool class. The thread pool would dynamically allocate threads to an instantiation specified limit, allow threads to be requested in blocking and non-blocking fashion and maintain thread state.

==== Tasks ====
Tasks are concurrent work units. Each Task may be executed concurrently and may be grouped. A process may wait for all tasks to be completed, or request asynchronous notification.

==== Parallel Loops ====
Inspired by TBB, a parallel loop would automatically break a large number of iterations across threads in a ''scatter-gather'' pattern. An object used for looping would only need to have a particular method, or may need to be a particular subclass.

← Older revision		Revision as of 18:07, 10 July 2017
Line 1:		Line 1:
−	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [~~http~~://www.slicer.org/~~slicerWiki/index.php~~/Slicer3:ThreadingToolKit here]</font></big>	+	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:ThreadingToolKit here]</font></big>

← Older revision		Revision as of 17:51, 20 May 2008
Line 1:		Line 1:
−	~~=== Purpose ===~~	+	<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [http://www.slicer.org/slicerWiki/index.php/Slicer3:ThreadingToolKit here]</font></big>
−
−	~~Just as the [[Slicer3~~:~~Execution_Model\| Execution Model]] has enabled algorithm developers~~ to ~~rapidly integrate their software into Slicer3, the purpose of~~ the ~~Threading ToolKit (TTK) is to enable algorithm and application developers to easily take advantage of multi core threaded environments~~.
−
−	=~~== Goals ===~~
−
−	* Provide building blocks inspired by [http://www.~~openmp~~.org ~~OpenMP], [http:~~//~~java.sun~~.~~com~~/~~docs/books/tutorial/essential/concurrency/index.html Java's concurrency model], and [http~~:~~//osstbb.intel.com/ Intel's Threading Building Blocks~~].
−	* Provide a cross platform C++ implementation for
−	** POSIX pthreads
−	** Windows threading
−	** Single threaded implementation
−	* Attempt a header only implementation, to minimize developer overhead
−
−	~~=== Design thoughts ===~~
−
−	~~==== Thread Pool ====~~
−	Provide a thread pool class. The thread pool would dynamically allocate threads to an instantiation specified limit, allow threads to be requested in blocking and non-blocking fashion and maintain thread state.
−
−	~~==== Tasks ====~~
−	~~Tasks are concurrent work units. Each Task may be executed concurrently and may be grouped. A process may wait for all tasks to be completed, or request asynchronous notification.~~
−
−	~~==== Parallel Loops ====~~
−	Inspired by TBB, a parallel loop would automatically break a large number of iterations across threads in a ''scatter-gather'' pattern. An object used for looping would only need to have a particular method, or may need to be a particular subclass.
−
−	~~== Related Links ==~~
−	* http://www.dmoz.org/Computers/Programming/~~Threads~~/

← Older revision		Revision as of 15:32, 3 August 2007
Line 22:		Line 22:
	==== Parallel Loops ====		==== Parallel Loops ====
	Inspired by TBB, a parallel loop would automatically break a large number of iterations across threads in a ''scatter-gather'' pattern. An object used for looping would only need to have a particular method, or may need to be a particular subclass.		Inspired by TBB, a parallel loop would automatically break a large number of iterations across threads in a ''scatter-gather'' pattern. An object used for looping would only need to have a particular method, or may need to be a particular subclass.
		+
		+	== Related Links ==
		+	* http://www.dmoz.org/Computers/Programming/Threads/

← Older revision	Revision as of 17:51, 20 May 2008
(No difference)