Starpu - OOC
Try to remove direct use of StarPU in OOC directory.
Merge request reports
Activity
@thibault I did some checks, but I'm not sure I have been checking the OOC correctly. Can you have a look please and let me know if that works. Thanks
I'm actually surprised by this source code. What I had documented in 3e6305c6 was to define STARPU_DISK_SWAP, STARPU_DISK_SWAP_BACKEND, and STARPU_LIMIT_CPU_MEM variables, STARPU_DISK_SWAP notably allows to set the path where to store the ooc matrix.
I understand that Chameleon would rather have non-STARPU-named variables, so perhaps the chameleon initialization function could rather set the STARPU-named variables from Chameleon-named variables? Or from Chameleon options.
-
I never touch this code, and I don't know who pushed it. My point here is to make things move forward and quickly get rid of StarPU references in examples/timings directory :). If you tell me this is incorrect, thus it may be worth removing completely this code, to redo it later more correctly.
Well, not completely (we still need the -ooc option to get proper behavior), but yes I guess we can drop most of it and let users use STARPU variables for now (but again the documentation from 3e6305c6 got lost and needs to be reintroduced)
added 12 commits
Toggle commit listadded 30 commits
Toggle commit listadded 11 commits
-
b172de5f...75123d32 - 4 commits from branch
solverstack:master - fffe7f82 - Add a RUNTIME_set function to enable ooc within runtime and not outside
- d8ecdd75 - Fix size of value
- 7a4f761e - A bunch of cleanup
- d3c23262 - Minor
- 253b05a5 - Fix print
- 6018130c - Add missing doc
- 24d7e019 - Remove the OOC example, and the modification made for this example
Toggle commit list-
b172de5f...75123d32 - 4 commits from branch
added 1 commit
- ad978258 - Change the set of timing to test new functions and test OOC
-
@thibault Just in case you didn't receive the message.
mentioned in commit 15ec5abc
