From: Martin Quinson <martin.quinson@ens-rennes.fr>
Date: Wed, 5 Jun 2019 15:07:28 +0000 (+0200)
Subject: LMM: rename sharing_weight into sharing_penalty for sake of clarity
X-Git-Tag: v3.22.4~2
X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/76e8bf7e84d35a0d3442f7f1e9ba5927db1d4fb5?hp=76e8bf7e84d35a0d3442f7f1e9ba5927db1d4fb5;ds=sidebyside

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.
---