MPS issue job003926

TitlePolicy is hard to work on
Assigned userGareth Rees
DescriptionThe policy parts of the MPS are hard to work on because the policy decisions are scattered across the code and so it is very hard to get an idea of what is going on. Policy decisions include:

(a) start a collection now?
(b) extend the arena now?
(c) purge spare committed memory now?
(d) compact the arena now?
(e) condemn which segments?
(f) scan another segment now?

Noted in planning meeting [1].
AnalysisA good first step would be to collect all the policy decisions into a single place, for example a new module (policy.c), without actually changing any behaviour. Then at least the scope of the problem will be clear.
How foundinspection
Evidence[1] <>
Created byGareth Rees
Created on2015-08-11 12:39:28
Last modified byGareth Rees
Last modified on2016-03-13 00:28:22
History2015-08-11 GDR Created.


Change Effect Date User Description
189330 closed 2016-02-25 21:46:11 Richard Brooksby Merging branch/2015-08-11/policy into master sources.