- 04 Dec, 2019 1 commit
-
-
FritzFlorian committed
-
- 29 Nov, 2019 1 commit
-
-
The start_chain property does not make sense, as chains are purely 'virtual', i.e. they only fully exist when walking through the computation (by patching them on important events). We initially added the property as a helper for better runtime and simpler implementation, but we think without it we will not get as much inconsistency in the runtime state. Performance can be 're-added' later on.
FritzFlorian committed
-
- 19 Nov, 2019 1 commit
-
-
Everything so far is untested. We only made sure tha fast path still seems to function correctly. Next up is writing tests for both the fast and slow path to then introduce the slow path. After that we can look at performance optimizations.
FritzFlorian committed
-
- 07 Nov, 2019 1 commit
-
-
This showcases the expected performance when a task executes a sub-tree without inference from other threads. We target to stay about 6x slower than a normal function call.
FritzFlorian committed
-
- 01 Oct, 2019 1 commit
-
-
FritzFlorian committed
-
- 16 Sep, 2019 1 commit
-
-
This allows us to more easily handle them and makes their interface closer to std::thread.
FritzFlorian committed
-
- 02 Sep, 2019 1 commit
-
-
The scheduler yields if it failed to steal any work due to the task lists being empty. This should improve performance on multiprogrammed systems, as it potentially makes room for other worker threads which still have work to perform.
FritzFlorian committed
-
- 01 Aug, 2019 2 commits
-
-
FritzFlorian committed
-
This allows the stack and deque class to use the same offset, making it work better with each other.
FritzFlorian committed
-
- 31 Jul, 2019 1 commit
-
-
FritzFlorian committed
-
- 18 Jun, 2019 1 commit
-
-
Threads must be joined on scheduler termination and tasks must be pushed onto the stack to allow better memory management.
FritzFlorian committed
-
- 14 Jun, 2019 3 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
FritzFlorian committed
-
- 12 Jun, 2019 3 commits
-
-
FritzFlorian committed
-
This seems to be only possible with two different function names, as variadic arguments and default arguments wont work together.
FritzFlorian committed -
FritzFlorian committed
-
- 06 Jun, 2019 2 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
- 05 Jun, 2019 1 commit
-
-
FritzFlorian committed
-
- 04 Jun, 2019 1 commit
-
-
Please note that this does currently not execute, but only removed the 'old aspecs'. We are still missing launching the root fork_join task.
FritzFlorian committed
-
- 13 May, 2019 1 commit
-
-
FritzFlorian committed
-
- 30 Apr, 2019 1 commit
-
-
FritzFlorian committed
-
- 17 Apr, 2019 1 commit
-
-
FritzFlorian committed
-
- 12 Apr, 2019 1 commit
-
-
FritzFlorian committed
-
- 09 Apr, 2019 2 commits
-
-
FritzFlorian committed
-
We do this to properly separate the cache alginment logic in the next step, allowing us to port all cache aligned objects without worrying about portability.
FritzFlorian committed
-
- 05 Apr, 2019 1 commit
-
-
This lead to some bug-fixes that covered move constructors not correctly assigning memory. We might clean this up further by only allowing in place creation of these types (placement new).
FritzFlorian committed
-
- 02 Apr, 2019 2 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
- 01 Apr, 2019 3 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
FritzFlorian committed
-
- 25 Mar, 2019 1 commit
-
-
This will be used for storing thread tasks aligned in continous memory, allowing different theads to work on the data without interfearing.
FritzFlorian committed
-
- 21 Mar, 2019 1 commit
-
-
FritzFlorian committed
-
- 20 Mar, 2019 3 commits
-
-
FritzFlorian committed
-
FritzFlorian committed
-
This requires the user to explicitly manage the storage duration/place of the thread local state, making a fine grained memory allocation simpler.
FritzFlorian committed
-
- 19 Mar, 2019 2 commits
-
-
FritzFlorian committed
-
The local storage per thread is only a pointer, this must be assigned AFTER the local storage object has moved to it's final location (e.g. on the stack of the caller). We might even change this a little further in the future to make the location of the state object more transparent.
FritzFlorian committed
-