diff --git a/mps/manual/wiki/refman_add.html b/mps/manual/wiki/refman_add.html index bc7d950c3e9..1bdea0858a6 100644 --- a/mps/manual/wiki/refman_add.html +++ b/mps/manual/wiki/refman_add.html @@ -53,7 +53,7 @@

Addenda

-

mps_class_amc, mps_class_ams: chain parameter

+

new parameter "chain" required for mps_class_amc, mps_class_ams

Create a chain with mps_chain_create, and pass it as argument to mps_pool_create for these two pool classes.

@@ -61,10 +61,18 @@

Pool class AMC is generational: the chain specifies capacity and predicted mortality of each generation. These capacities are not limits: they are used for scheduling collection of the AMC objects.

+

The way chains affect garbage collection is discussed in the GC Story article.

-

mps_arena_step and mps_arena_start_collect

-

See:

+

new functions: mps_arena_step, mps_arena_start_collect

+ +

When the client has some idle-time, it is permitted to call mps_arena_step(arena, interval, multiplier) to allow MPS to do collection work. The "interval" argument (units: seconds) specifies how much time the MPS is permitted to take with this mps_arena_step call. The "multiplier" argument specifies how many further similar calls to mps_arena_step the Client expects to make in this period of idle time. The idea is that the MPS should return before "interval" is exhausted, and should only eagerly commence long-duration operations that consume CPU (such as a full collection) if those operations are expected to be completed within "multiplier * interval" seconds.

+ +

Note that mps_arena_step will still step, even if the arena has been clamped. This is to allow a client to advance a collection only at these mps_arena_step points (but note that barrier hits will also cause collection work).

+ +

The client is permitted to request a full collection with mps_arena_start_collect. The MPS returns 'asynchronously' from this call, usually before full collection has completed. (Contrast the mps_arena_collect call, which does not return until the full collection has completed). Work on the full collection then proceeds incrementally, just as it does when the MPS schedules a full collection automatically.

+ +

Fuller documentation is currently only in email. See:

  1. http://info.ravenbrook.com/mail/2002/07/01/20-46-08/0.txt @@ -80,13 +88,13 @@
-

Note that mps_arena_step will still step, even if the arena has been clamped. This is to allow a client to advance a collection only at these mps_arena_step points (but note that barrier hits will also cause collection work).

-

B. Document History

-  2006-11-28  RHSK  Created: chain for AMC and AMS; mps_arena_step and mps_arena_start_collect.
+  2006-11-28  RHSK  Created: chain for AMC and AMS; mps_arena_step 
+                    and mps_arena_start_collect.
+  2006-12-29  RHSK  More comments on chain and arena_start/_step.