-* segfault with ./loba cluster1000.xml -N64 -a fairstrategy
-
- this is a deadlock occuring when:
- - a process is in the finalize stage;
- - all processes but one are blocked on receive;
- - the process that is still running owns all the remaining load,
- and sends it all to the finalizing process, and then goes in
- blocking receive.
- The finalizing process receives the load, and blocks again,
- waiting for a close message.
- All processes are then blocked, and non-one is able to see that
- there is no more load in the system!
-
-* verify bookkeeping version.
-
* add several metrics
- - flops (total, avg, stddev)
- - message exchanges (number, volume)
+ - message exchanges : number/volume of sent/received data/ctrl messages
-* add options -j/-J : minimum number of iterations ?
+* for automatic process topology,
+ -> implement some random initial distribution of load
-* add a variant to (not) change neighbor load information at send.
+* implement makhoul2
-* implement loba_* algorithms (start with some trivial one)
+* add options -j/-J : minimum number of iterations?
-* for automatic process topology,
- -> implement some random initial distribution of load
+* add options -f/-F : termination based on flops achieved?
-* add synchronized mode
+* implement loba_* algorithms (start with some trivial one)
-* translate README file?
+* add synchronized mode? NO
+* add a variant to (not) change neighbor load information at send? NO
+* translate README file? NOT URGENT
