Cédric Augonnet
|
25a0df2747
by default, a task does not use tags, and it is asynchronous
|
16 years ago |
Cédric Augonnet
|
414f1e8c28
cleanup the incrementer_runtime.c file to make it as simple as possible
|
16 years ago |
Cédric Augonnet
|
a3dfc2ea41
Add an example where it is possible to use StarPU with the runtime API.
|
16 years ago |
Cédric Augonnet
|
77b673df3d
minor cleanups of the examples
|
16 years ago |
Cédric Augonnet
|
841dee46ef
While removing a tag, protect the hierarchical table on the one hand, and the
|
16 years ago |
Cédric Augonnet
|
935a57a4e9
missed one chunk of the previous patch
|
16 years ago |
Cédric Augonnet
|
34bffe6fe3
accessed to tag->state have to be protected
|
16 years ago |
Cédric Augonnet
|
53b76fc51b
Notify_dependencies may free the completion group structure while we still have
|
16 years ago |
Cédric Augonnet
|
71646ef288
Protect tags when they are notified of the termination of one of their deps.
|
16 years ago |
Cédric Augonnet
|
54b4d86198
Continue to cleanup the handling of tasks dependencies, there are still issues.
|
16 years ago |
Cédric Augonnet
|
5cecf770ab
Start to reorganize the handling of tasks dependencies during task submission.
|
16 years ago |
Cédric Augonnet
|
1afb01e8cd
also install the tag_example3 example
|
16 years ago |
Cédric Augonnet
|
36e824717a
Add a new test (equivalent to tag_example2, but task are submitted in the
|
16 years ago |
Cédric Augonnet
|
69c17771ce
we must not set the is_submitted flag until we are sure nobody is going to
|
16 years ago |
Cédric Augonnet
|
adab8c8c23
It is possible that a task has not been submitted even if its (tags)
|
16 years ago |
Cédric Augonnet
|
f6afef5b29
Cosmetic cleanups, change the output of [a]sync-tasks-overhead into something
|
16 years ago |
Cédric Augonnet
|
fdf2fb6ee2
Thanks to CUDA driver and runtime APIs not liking each other, and CUBLAS using
|
16 years ago |
Cédric Augonnet
|
27fa5c1d8e
do not export fetch_data
|
16 years ago |
Cédric Augonnet
|
5bcc626e42
Add an optional "deinit_sched" method in the scheduling policy interface.
|
16 years ago |
Cédric Augonnet
|
2ad17cc384
cleanup the lists of memory requests at the termination of StarPU
|
16 years ago |
Cédric Augonnet
|
f982d23b5c
perhaps tasks that have been submitted are more likely to be completed ... :)
|
16 years ago |
Cédric Augonnet
|
22875839ef
Add a new test to make sure tags and the starpu_tag_wait* API is behaving
|
16 years ago |
Samuel Thibault
|
ce07f0c356
minor fixes
|
16 years ago |
Cédric Augonnet
|
334afa8703
Let the user specify the scheduling policy using command line in the
|
16 years ago |
Cédric Augonnet
|
3ef1ce23aa
In addition to the use of environment variables to specify the number of
|
16 years ago |
Cédric Augonnet
|
44dea0a457
add a preliminary README file.
|
16 years ago |
Cédric Augonnet
|
3215a6d117
Applications may wait until a set of tags are completed using the
|
16 years ago |
Cédric Augonnet
|
ac1ed7a69c
add the strassen example to the test suite
|
16 years ago |
Cédric Augonnet
|
933f9f1623
add the "incrementer" example to the test suite
|
16 years ago |
Cédric Augonnet
|
60a0d23fe8
Since the "task->cleanup" flag is set by default, there is no need to free the
|
16 years ago |