Logo AND Algorithmique Numérique Distribuée

Public GIT Repository
LMM: rename sharing_weight into sharing_penalty for sake of clarity
authorMartin Quinson <martin.quinson@ens-rennes.fr>
Wed, 5 Jun 2019 15:07:28 +0000 (17:07 +0200)
committerMartin Quinson <martin.quinson@ens-rennes.fr>
Wed, 5 Jun 2019 15:07:35 +0000 (17:07 +0200)
commit76e8bf7e84d35a0d3442f7f1e9ba5927db1d4fb5
tree17a8b4f15a2c926f307c84cb41a71c49c1094882
parent160df614083997dc8f03750ff3ceaff458fa3fe0
LMM: rename sharing_weight into sharing_penalty for sake of clarity

This is similar to what just happened in surf yesterday. It allows:
  -   cnst.usage_ += elem.consumption_weight / elem.variable->sharing_weight_;
  +   cnst.usage_ += elem.consumption_weight / elem.variable->sharing_penalty_;
which seems far more understandable to me.

I'm glad I finally got the will to do this boooooring cleanup, after
hours of being puzzled whether a sharing_weight is actually an
advantage or a drawback for the action in the LMM. The answer was "it
depends on whether you are in app, surf or LMM". Now, you know that
having a high priority is the opposite of having a high penalty, and
things should be less intricate.
13 files changed:
src/kernel/lmm/fair_bottleneck.cpp
src/kernel/lmm/maxmin.cpp
src/kernel/lmm/maxmin.hpp
src/kernel/resource/Action.cpp
src/surf/cpu_cas01.cpp
src/surf/cpu_interface.cpp
src/surf/network_cm02.cpp
src/surf/network_interface.hpp
src/surf/ptask_L07.cpp
src/surf/storage_n11.cpp
teshsuite/surf/lmm_usage/lmm_usage.cpp
teshsuite/surf/maxmin_bench/maxmin_bench_medium.tesh
teshsuite/surf/maxmin_bench/maxmin_bench_small.tesh