Glossary and References - Revision history

imported>Cnewburn: /* Task */

2017-03-18T22:46:47Z

Task

← Older revision		Revision as of 22:46, March 18, 2017
Line 26:		Line 26:

	Unit of execution that may be split into one or many tasklets.		Unit of execution that may be split into one or many tasklets.

			Open: some use a different term for units of execution that continue to completion vs. those that may stall while waiting on some other input.
			In particular, Qthreads and Argobots differ in terminology here.

			We wish to be able to (eventually) support tasks while may stall on some input, and have their resources preempted while they are not data ready.

	== Tasklet ==		== Tasklet ==

2017-03-18T22:44:24Z

Data destination, target

← Older revision		Revision as of 22:44, March 18, 2017
Line 14:		Line 14:
	The set of resources with which the source is associated is called the origin, e.g. the origin process, according to the MPI spec.		The set of resources with which the source is associated is called the origin, e.g. the origin process, according to the MPI spec.

	== Data ~~sink~~ ==		== Data destination, target ==

	Destination ~~for~~ data communication		Destination of data communication; where data is transferred to.
			The set of resources with which the destination is associated is called the target, e.g. the target process, according to the MPI spec.
			The corresponding term for target that hStreams uses is "sink."

	== Event ==		== Event ==

2017-03-18T22:42:49Z

Data source, origin

← Older revision		Revision as of 22:42, March 18, 2017
Line 9:		Line 9:
	* Resources management (compute, memory, …), e.g. allocation, physical materialization, deallocation/freeing		* Resources management (compute, memory, …), e.g. allocation, physical materialization, deallocation/freeing

	== Data source ==		== Data source, origin ==

	Originator of data communication		Originator of data communication; where data is transferred from.
			The set of resources with which the source is associated is called the origin, e.g. the origin process, according to the MPI spec.

	== Data sink ==		== Data sink ==

2017-01-17T16:47:54Z

New term: directory

← Older revision		Revision as of 16:47, January 17, 2017
Line 55:		Line 55:
	== Execution space ==		== Execution space ==
	== Memory space ==		== Memory space ==

			== Directory ==

			Look up service to identify a sink or source in a lower-level communication substrate.

			''It might be wise to externalize a global directory service and make it an optional part of the reference implementation. By so doing, we allow a cottage industry to create competing implementation of such look-up services that serve specific needs of applications, hardware, or the middleware.''

2017-01-17T16:46:45Z

Strawman definitions

← Older revision		Revision as of 16:46, January 17, 2017
Line 9:		Line 9:
	* Resources management (compute, memory, …), e.g. allocation, physical materialization, deallocation/freeing		* Resources management (compute, memory, …), e.g. allocation, physical materialization, deallocation/freeing

	== Data source, data sink ==		== Data source ==

			Originator of data communication

			== Data sink ==

			Destination for data communication

	== Event ==		== Event ==
	Handle for an object that tracks whether sync has been triggered, that may be used for communicating the fulfillment of data or control dependences		Handle for an object that tracks whether sync has been triggered, that may be used for communicating the fulfillment of data or control dependences

2017-01-17T16:45:53Z

Strawman definitions

← Older revision		Revision as of 16:45, January 17, 2017
Line 13:		Line 13:
	Handle for an object that tracks whether sync has been triggered, that may be used for communicating the fulfillment of data or control dependences		Handle for an object that tracks whether sync has been triggered, that may be used for communicating the fulfillment of data or control dependences
	== Dependence ==		== Dependence ==
	== Task, Tasklet ==		== Task ==

			Unit of execution that may be split into one or many tasklets.

			== Tasklet ==

			Non-decomposable unit of execution that performs useful work.

	== Hierarchical ==		== Hierarchical ==
	* A hierarchy may have some number of levels, some number of actions at each level		* A hierarchy may have some number of levels, some number of actions at each level

2017-01-17T16:31:22Z

@@ Line 1: / Line 1: @@
-*Action
+Below is a list of terms and concepts that could be defined for common usage.  Feel free to add to the list of terms, and to begin offering possible definitions.
 *Data source, data sink
-*Event
+== Action ==
-*Dependence
+Operation that is executed using resources, ordered in a way that maintains dependences, has a specific beginning and end (we need to make this more rigorous)
-*Task, Tasklet
+Actions may be a different kinds.
-*Hierarchical
+* Compute (task)
-*Heterogeneous
+* Data movement
-*Asynchronous
+* Control (synchronization, conditional/predication)
-*Execution space
+* Resources management (compute, memory, …), e.g. allocation, physical materialization, deallocation/freeing
-*Memory space

2017-01-17T15:53:11Z

2017-01-17T05:33:39Z

2017-01-17T05:25:53Z

Introduce terms to be defined.

New page

Action
Event
Dependence
Task
Hierarchical
Heterogeneous
Asynchronous
Place/Domain