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
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
.. index::
   single: MFS
   single: pool class; MFS

.. _pool-mfs:

MFS (Manual Fixed Small)
========================

**MFS** is an :term:`manually managed <manual memory management>`
:term:`pool class` for small objects of fixed size.

Unlike other manual pool classes, it is not subject to :term:`internal
fragmentation`.

The implementation is very simple: unlike other :term:`pool classes`
which store their control structures separately from the allocated
blocks, MFS maintains a stack of free blocks using a pointer in the
free block. :c:func:`mps_alloc` pops this stack and :c:func:`mps_free`
pushes it.


.. index::
   single: MFS; properties

MFS properties
--------------

* Supports allocation via :c:func:`mps_alloc` and deallocation via
  :c:func:`mps_free`.

* Does not support allocation via :term:`allocation points`.

* Does not support :term:`allocation frames`.

* Supports :term:`segregated allocation caches` (but using one would
  be pointless, since all blocks are the same size).

* There are no garbage collections in this pool.

* Blocks may not contain :term:`references` to blocks in automatically
  managed pools (unless these are registered as :term:`roots`).

* Allocations are fixed in size.

* The :term:`alignment` of blocks is not configurable: it is the
  :term:`natural alignment` of the platform (see
  :c:macro:`MPS_PF_ALIGN`).

* Blocks do not have :term:`dependent objects`.

* Blocks are not automatically :term:`reclaimed`.

* Blocks are not :term:`scanned <scan>`.

* Blocks are not protected by :term:`barriers (1)`.

* Blocks do not :term:`move <moving garbage collector>`.

* Blocks may not be registered for :term:`finalization`.

* Blocks must not belong to an :term:`object format`.


.. index::
   single: MFS; interface

MFS interface
-------------

::

   #include "mpscmfs.h"

.. c:function:: mps_class_t mps_class_mfs(void)

    Return the :term:`pool class` for an MFS (Manual Fixed Small)
    :term:`pool`.

    When creating an MFS pool, :c:func:`mps_pool_create_k` requires
    one :term:`keyword argument`:

    * :c:macro:`MPS_KEY_MFS_UNIT_SIZE` (type :c:type:`size_t`) is the
      :term:`size` of blocks that will be allocated from this pool, in
      :term:`bytes (1)`. It must be at least one :term:`word`.

    In addition, :c:func:`mps_pool_create_k` may take:

    * :c:macro:`MPS_KEY_EXTEND_BY` (type :c:type:`size_t`, default 65536) is the
      :term:`size` of segment that the pool will request from the
      :term:`arena`. It must be at least as big as the unit size
      specified by the :c:macro:`MPS_KEY_MFS_UNIT_SIZE` keyword
      argument. If this is not a multiple of the unit size, there will
      be wasted space in each segment.

    For example::

        MPS_ARGS_BEGIN(args) {
            MPS_ARGS_ADD(ARGS, MPS_KEY_MFS_UNIT_SIZE, 1024);
            MPS_ARGS_ADD(ARGS, MPS_KEY_EXTEND_BY, 1024 * 1024);
            MPS_ARGS_DONE(args);
            res = mps_pool_create_k(&pool, arena, mps_class_mfs(), args);
        } MPS_ARGS_END(args);

    .. deprecated:: starting with version 1.112.

        When using :c:func:`mps_pool_create`, pass the segment size and
        unit size like this::

            mps_res_t mps_pool_create(mps_pool_t *pool_o, mps_arena_t arena, 
                                      mps_class_t mps_class_mfs(),
                                      mps_size_t extend_size,
                                      mps_size_t unit_size)