parsec
parsec copied to clipboard
PaRSEC is a generic framework for architecture aware scheduling and management of micro-tasks on distributed, GPU accelerated, many-core heterogeneous architectures. PaRSEC assigns computation threads...
## Description PaRSEC deals with NUMA machines by ignoring any NUMA issues. This leads to sub-optimal performance on nearly all modern architectures, especially on larger machines with many NUMA zones...
Collection of various issues in different MCA sched components; I'll make a PR to fix these at some point. - LFQ - Currently iterates over local queue twice if local...
## Description When debugging memory leaks, I used the returned pointer as the ID for events. That pointer is temporally unique (at any given time, it represents a single allocation),...
Would it be possible to expose the total data, a task is operating on, to the profiler. I need this information when profiling it for action EXEC_BEGIN and EXEC_END.
## Description With TTG, PaRSEC has gained a C++ frontend and with it some of the issues specific to C++. C++ compilers typically cannot see inside PaRSEC's C interface and...
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/231) by Thomas Herault (Bitbucket: [herault](https://bitbucket.org/herault), GitHub: [therault](https://github.com/therault)).** ---------------------------------------- It appears that if ```shell OMP_PROC_BIND=true ``` is set in the environment, and we link with libgomp, ```c parsec_init() ```...
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/181) by George Bosilca (Bitbucket: [bosilca](https://bitbucket.org/bosilca), GitHub: [bosilca](https://github.com/bosilca)).** ---------------------------------------- As of today only the communication thread can be bound on a set of cores, all other PaRSEC threads must...
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/178) by Yu Pei (Bitbucket: [Yu Pei](https://bitbucket.org/Yu Pei), ).** ---------------------------------------- When use DTD TILE_OF to access data but at the same time also use DONT_TRACK flag (doing my own...
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/151) by Reazul Hoque (Bitbucket: [rhoque_icl](https://bitbucket.org/rhoque_icl), ).** ---------------------------------------- We need unique ID for data collection, the same we have for task collection.
**[Original report](https://bitbucket.org/icldistcomp/parsec/issue/173) by Thomas Herault (Bitbucket: [herault](https://bitbucket.org/herault), GitHub: [therault](https://github.com/therault)).** ---------------------------------------- Recent work on the BlueGene/Q system showed that the binding capability is limited. * Binding using hwloc (or other options)...