1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
.. highlight:: none


.. index::
   pair: fail-over allocator; design

.. _design-failover:


Fail-over allocator
===================

.. mps:prefix:: design.mps.failover


Introduction
------------

:mps:tag:`intro` This is the design of the fail-over allocator, a data
structure for the management of address ranges.

:mps:tag:`readership` This document is intended for any MPS developer.

:mps:tag:`source` design.mps.land_, design.mps.poolmvt_, design.mps.poolmvff_.

:mps:tag:`overview` The fail-over allocator combines two *land* instances.
It stores address ranges in one of the lands (the *primary*) unless
insertion fails, in which case it falls back to the other (the
*secondary*). The purpose is to be able to combine two lands with
different properties: with a CBS_ for the primary and a
Freelist_ for the secondary, operations are fast so long as there
is memory to allocate new nodes in the CBS_, but operations can
continue using the Freelist_ when memory is low.

.. _CBS: cbs
.. _Freelist: freelist
.. _design.mps.land: land.html
.. _design.mps.poolmvt: poolmvt.html
.. _design.mps.poolmvff: poolmvff.html


Interface
---------

:mps:tag:`land` The fail-over allocator is an implementation of the *land*
abstract data type, so the interface consists of the generic functions
for lands. See design.mps.land_.


Types
.....

.. c:type:: struct FailoverStruct *Failover

:mps:tag:`type.failover` The type of fail-over allocator structures. A
:c:type:`FailoverStruct` is typically embedded in another structure.


Classes
.......

:mps:tag:`class` ``CLASS(Failover)`` is the fail-over allocator class, a
subclass of ``CLASS(Land)`` suitable for passing to :c:func:`LandInit()`.


Keyword arguments
.................

When initializing a fail-over allocator, :c:func:`LandInit()` requires these
two keyword arguments:

* ``FailoverPrimary`` (type :c:type:`Land`) is the primary land.

* ``FailoverSecondary`` (type :c:type:`Land`) is the secondary land.


Implementation
--------------

:mps:tag:`impl.assume` The implementation assumes that the primary is fast
but space-hungry (a CBS_) and the secondary is slow but space-frugal
(a Freelist_). This assumption is used in the following places:

:mps:tag:`impl.assume.flush` The fail-over allocator attempts to flush the
secondary to the primary before any operation, in order to benefit
from the speed of the primary wherever possible. In the normal case
where the secondary is empty this is cheap.

:mps:tag:`impl.assume.delete` When deletion of a range on the primary fails
due to lack of memory, we assume that this can only happen when there
are splinters on both sides of the deleted range, one of which needs
to be allocated a new node (this is the case for CBS_), and that
therefore the following procedure will be effective: first, delete the
enclosing range from the primary (leaving no splinters and thus
requiring no allocation), and re-insert the splinters (failing over to
the secondary if necessary).