2 .\" Copyright (c) 2001 Dag-Erling Coïdan Smørgrav
3 .\" All rights reserved.
5 .\" Redistribution and use in source and binary forms, with or without
6 .\" modification, are permitted provided that the following conditions
8 .\" 1. Redistributions of source code must retain the above copyright
9 .\" notice, this list of conditions and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
14 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
15 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
46 .Fa "char *name" "int size"
47 .Fa "uma_ctor ctor" "uma_dtor dtor" "uma_init uminit" "uma_fini fini"
48 .Fa "int align" "u_int16_t flags"
51 .Fn uma_zalloc "uma_zone_t zone" "int flags"
53 .Fn uma_zalloc_arg "uma_zone_t zone" "void *arg" "int flags"
55 .Fn uma_zfree "uma_zone_t zone" "void *item"
57 .Fn uma_zfree_arg "uma_zone_t zone" "void *item" "void *arg"
59 .Fn uma_zdestroy "uma_zone_t zone"
61 .Fn uma_zone_set_max "uma_zone_t zone" "int nitems"
63 The zone allocator provides an efficient interface for managing
64 dynamically-sized collections of items of similar size.
65 The zone allocator can work with preallocated zones as well as with
66 runtime-allocated ones, and is therefore available much earlier in the
67 boot process than other memory management routines.
69 A zone is an extensible collection of items of identical size.
70 The zone allocator keeps track of which items are in use and which
71 are not, and provides functions for allocating items from the zone and
72 for releasing them back (which makes them available for later use).
74 After the first allocation of an item,
75 it will have been cleared to zeroes, however subsequent allocations
76 will retain the contents as of the last free.
80 function creates a new zone from which items may then be allocated from.
83 argument is a text name of the zone for debugging and stats; this memory
84 should not be freed until the zone has been deallocated.
90 arguments are callback functions that are called by
91 the uma subsystem at the time of the call to
96 Their purpose is to provide hooks for initializing or
97 destroying things that need to be done at the time of the allocation
98 or release of a resource.
104 might be to adjust a global count of the number of objects allocated.
110 arguments are used to optimize the allocation of
111 objects from the zone.
112 They are called by the uma subsystem whenever
113 it needs to allocate or free several items to satisfy requests or memory
119 callbacks might be to
120 initialize and destroy mutexes contained within the object.
122 allow one to re-use already initialized mutexes when an object is returned
123 from the uma subsystem's object cache.
124 They are not called on each call to
128 but rather in a batch mode on several objects.
130 To allocate an item from a zone, simply call
132 with a pointer to that zone
135 argument to selected flags as documented in
137 It will return a pointer to an item if successful,
140 in the rare case where all items in the zone are in use and the
141 allocator is unable to grow the zone
146 Items are released back to the zone from which they were allocated by
149 with a pointer to the zone and a pointer to the item.
156 specify an argument for the
160 functions, respectively.
164 can be destroyed using
166 freeing all memory that was allocated for the zone.
167 All items allocated from the zone with
169 must have been freed with
175 is to limit the maximum amount of memory that the system can dedicated
176 toward the zone specified by the
181 argument gives the upper limit of items in the zone.
182 This limits the total number of items in the zone which includes:
183 allocated items, free items and free items in the per-cpu caches.
184 On systems with more than one CPU it may not be possible to allocate
185 the specified number of items even when there is no shortage of memory,
186 because all of the remaining free items may be in the caches of the
187 other CPUs when the limit is hit.
191 function returns a pointer to an item, or
193 if the zone ran out of unused items and the allocator was unable to
198 The zone allocator first appeared in
200 It was radically changed in
202 to function as a slab allocator.
205 The zone allocator was written by
207 The zone allocator was rewritten in large parts by
208 .An Jeff Roberson Aq jeff@FreeBSD.org
209 to function as a slab allocator.
211 This manual page was written by
212 .An Dag-Erling Sm\(/orgrav Aq des@FreeBSD.org .
214 .An Jeroen Ruigrok van der Werven Aq asmodai@FreeBSD.org .