2001-01-27 19:13:08 +00:00
|
|
|
.\"-
|
2011-05-22 14:03:30 +00:00
|
|
|
.\" Copyright (c) 2001 Dag-Erling Coïdan Smørgrav
|
2001-01-27 19:13:08 +00:00
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
|
|
|
.\" $FreeBSD$
|
|
|
|
.\"
|
Make UMA and malloc(9) return non-executable memory in most cases.
Most kernel memory that is allocated after boot does not need to be
executable. There are a few exceptions. For example, kernel modules
do need executable memory, but they don't use UMA or malloc(9). The
BPF JIT compiler also needs executable memory and did use malloc(9)
until r317072.
(Note that a side effect of r316767 was that the "small allocation"
path in UMA on amd64 already returned non-executable memory. This
meant that some calls to malloc(9) or the UMA zone(9) allocator could
return executable memory, while others could return non-executable
memory. This change makes the behavior consistent.)
This change makes malloc(9) return non-executable memory unless the new
M_EXEC flag is specified. After this change, the UMA zone(9) allocator
will always return non-executable memory, and a KASSERT will catch
attempts to use the M_EXEC flag to allocate executable memory using
uma_zalloc() or its variants.
Allocations that do need executable memory have various choices. They
may use the M_EXEC flag to malloc(9), or they may use a different VM
interfact to obtain executable pages.
Now that malloc(9) again allows executable allocations, this change also
reverts most of r317072.
PR: 228927
Reviewed by: alc, kib, markj, jhb (previous version)
Sponsored by: Netflix
Differential Revision: https://reviews.freebsd.org/D15691
2018-06-13 17:04:41 +00:00
|
|
|
.Dd June 13, 2018
|
2001-01-27 19:13:08 +00:00
|
|
|
.Dt ZONE 9
|
|
|
|
.Os
|
|
|
|
.Sh NAME
|
2002-05-18 11:12:02 +00:00
|
|
|
.Nm uma_zcreate ,
|
2002-04-30 12:45:31 +00:00
|
|
|
.Nm uma_zalloc ,
|
2008-06-19 18:33:38 +00:00
|
|
|
.Nm uma_zalloc_arg ,
|
2018-03-24 23:58:44 +00:00
|
|
|
.Nm uma_zalloc_domain ,
|
2002-04-30 12:45:31 +00:00
|
|
|
.Nm uma_zfree ,
|
2008-06-19 18:33:38 +00:00
|
|
|
.Nm uma_zfree_arg ,
|
2018-03-24 23:58:44 +00:00
|
|
|
.Nm uma_zfree_domain ,
|
2003-07-21 14:20:58 +00:00
|
|
|
.Nm uma_zdestroy ,
|
2018-03-17 11:41:06 +00:00
|
|
|
.Nm uma_zone_set_max ,
|
|
|
|
.Nm uma_zone_get_max ,
|
|
|
|
.Nm uma_zone_get_cur ,
|
|
|
|
.Nm uma_zone_set_warning ,
|
2015-12-20 02:05:33 +00:00
|
|
|
.Nm uma_zone_set_maxaction
|
2001-01-29 08:59:30 +00:00
|
|
|
.Nd zone allocator
|
2001-01-27 19:13:08 +00:00
|
|
|
.Sh SYNOPSIS
|
2001-10-01 16:09:29 +00:00
|
|
|
.In sys/param.h
|
2001-12-26 23:14:04 +00:00
|
|
|
.In sys/queue.h
|
2002-04-30 08:51:42 +00:00
|
|
|
.In vm/uma.h
|
2002-05-18 11:12:02 +00:00
|
|
|
.Ft uma_zone_t
|
2002-05-30 11:37:39 +00:00
|
|
|
.Fo uma_zcreate
|
|
|
|
.Fa "char *name" "int size"
|
|
|
|
.Fa "uma_ctor ctor" "uma_dtor dtor" "uma_init uminit" "uma_fini fini"
|
2012-02-12 18:29:56 +00:00
|
|
|
.Fa "int align" "uint16_t flags"
|
2002-05-30 11:37:39 +00:00
|
|
|
.Fc
|
|
|
|
.Ft "void *"
|
|
|
|
.Fn uma_zalloc "uma_zone_t zone" "int flags"
|
2008-06-19 18:33:38 +00:00
|
|
|
.Ft "void *"
|
|
|
|
.Fn uma_zalloc_arg "uma_zone_t zone" "void *arg" "int flags"
|
2018-03-24 23:58:44 +00:00
|
|
|
.Ft "void *"
|
|
|
|
.Fn uma_zalloc_domain "uma_zone_t zone" "void *arg" "int domain" "int flags"
|
2001-01-27 19:13:08 +00:00
|
|
|
.Ft void
|
2002-04-30 13:03:28 +00:00
|
|
|
.Fn uma_zfree "uma_zone_t zone" "void *item"
|
2001-08-09 16:01:27 +00:00
|
|
|
.Ft void
|
2008-06-19 18:33:38 +00:00
|
|
|
.Fn uma_zfree_arg "uma_zone_t zone" "void *item" "void *arg"
|
|
|
|
.Ft void
|
2018-03-24 23:58:44 +00:00
|
|
|
.Fn uma_zfree_domain "uma_zone_t zone" "void *item" "void *arg"
|
|
|
|
.Ft void
|
2002-04-30 13:03:28 +00:00
|
|
|
.Fn uma_zdestroy "uma_zone_t zone"
|
2010-10-16 04:41:45 +00:00
|
|
|
.Ft int
|
2003-07-21 14:20:58 +00:00
|
|
|
.Fn uma_zone_set_max "uma_zone_t zone" "int nitems"
|
2010-10-16 04:14:45 +00:00
|
|
|
.Ft int
|
|
|
|
.Fn uma_zone_get_max "uma_zone_t zone"
|
|
|
|
.Ft int
|
|
|
|
.Fn uma_zone_get_cur "uma_zone_t zone"
|
2012-12-07 22:27:13 +00:00
|
|
|
.Ft void
|
|
|
|
.Fn uma_zone_set_warning "uma_zone_t zone" "const char *warning"
|
2015-12-20 02:05:33 +00:00
|
|
|
.Ft void
|
|
|
|
.Fn uma_zone_set_maxaction "uma_zone_t zone" "void (*maxaction)(uma_zone_t)"
|
2014-02-07 14:29:03 +00:00
|
|
|
.In sys/sysctl.h
|
|
|
|
.Fn SYSCTL_UMA_MAX parent nbr name access zone descr
|
|
|
|
.Fn SYSCTL_ADD_UMA_MAX ctx parent nbr name access zone descr
|
|
|
|
.Fn SYSCTL_UMA_CUR parent nbr name access zone descr
|
|
|
|
.Fn SYSCTL_ADD_UMA_CUR ctx parent nbr name access zone descr
|
2001-01-27 19:13:08 +00:00
|
|
|
.Sh DESCRIPTION
|
|
|
|
The zone allocator provides an efficient interface for managing
|
2018-03-24 23:58:44 +00:00
|
|
|
dynamically-sized collections of items of identical size.
|
2001-01-27 19:13:08 +00:00
|
|
|
The zone allocator can work with preallocated zones as well as with
|
|
|
|
runtime-allocated ones, and is therefore available much earlier in the
|
2018-03-24 23:58:44 +00:00
|
|
|
boot process than other memory management routines. The zone allocator
|
|
|
|
provides per-cpu allocation caches with linear scalability on SMP
|
|
|
|
systems as well as round-robin and first-touch policies for NUMA
|
|
|
|
systems.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Pp
|
|
|
|
A zone is an extensible collection of items of identical size.
|
|
|
|
The zone allocator keeps track of which items are in use and which
|
2002-04-30 09:38:52 +00:00
|
|
|
are not, and provides functions for allocating items from the zone and
|
2001-01-27 19:13:08 +00:00
|
|
|
for releasing them back (which makes them available for later use).
|
|
|
|
.Pp
|
2002-01-10 13:02:55 +00:00
|
|
|
After the first allocation of an item,
|
|
|
|
it will have been cleared to zeroes, however subsequent allocations
|
2006-10-02 07:27:00 +00:00
|
|
|
will retain the contents as of the last free.
|
2001-12-14 19:19:31 +00:00
|
|
|
.Pp
|
2002-05-18 11:12:02 +00:00
|
|
|
The
|
|
|
|
.Fn uma_zcreate
|
|
|
|
function creates a new zone from which items may then be allocated from.
|
|
|
|
The
|
|
|
|
.Fa name
|
|
|
|
argument is a text name of the zone for debugging and stats; this memory
|
|
|
|
should not be freed until the zone has been deallocated.
|
|
|
|
.Pp
|
2002-11-18 01:11:58 +00:00
|
|
|
The
|
|
|
|
.Fa ctor
|
|
|
|
and
|
|
|
|
.Fa dtor
|
|
|
|
arguments are callback functions that are called by
|
|
|
|
the uma subsystem at the time of the call to
|
|
|
|
.Fn uma_zalloc
|
|
|
|
and
|
|
|
|
.Fn uma_zfree
|
2002-11-29 11:39:20 +00:00
|
|
|
respectively.
|
|
|
|
Their purpose is to provide hooks for initializing or
|
2002-11-18 01:11:58 +00:00
|
|
|
destroying things that need to be done at the time of the allocation
|
2002-11-29 11:39:20 +00:00
|
|
|
or release of a resource.
|
2003-05-31 14:20:30 +00:00
|
|
|
A good usage for the
|
2002-11-18 01:11:58 +00:00
|
|
|
.Fa ctor
|
|
|
|
and
|
|
|
|
.Fa dtor
|
|
|
|
callbacks
|
|
|
|
might be to adjust a global count of the number of objects allocated.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fa uminit
|
|
|
|
and
|
|
|
|
.Fa fini
|
|
|
|
arguments are used to optimize the allocation of
|
2002-11-29 11:39:20 +00:00
|
|
|
objects from the zone.
|
|
|
|
They are called by the uma subsystem whenever
|
2002-11-18 01:11:58 +00:00
|
|
|
it needs to allocate or free several items to satisfy requests or memory
|
2002-11-29 11:39:20 +00:00
|
|
|
pressure.
|
|
|
|
A good use for the
|
|
|
|
.Fa uminit
|
|
|
|
and
|
|
|
|
.Fa fini
|
|
|
|
callbacks might be to
|
|
|
|
initialize and destroy mutexes contained within the object.
|
|
|
|
This would
|
2002-11-18 01:11:58 +00:00
|
|
|
allow one to re-use already initialized mutexes when an object is returned
|
2002-11-29 11:39:20 +00:00
|
|
|
from the uma subsystem's object cache.
|
|
|
|
They are not called on each call to
|
2002-11-18 01:11:58 +00:00
|
|
|
.Fn uma_zalloc
|
|
|
|
and
|
|
|
|
.Fn uma_zfree
|
|
|
|
but rather in a batch mode on several objects.
|
|
|
|
.Pp
|
2013-03-21 16:19:46 +00:00
|
|
|
The
|
|
|
|
.Fa flags
|
|
|
|
argument of the
|
|
|
|
.Fn uma_zcreate
|
|
|
|
is a subset of the following flags:
|
|
|
|
.Bl -tag -width "foo"
|
|
|
|
.It Dv UMA_ZONE_NOFREE
|
|
|
|
Slabs of the zone are never returned back to VM.
|
|
|
|
.It Dv UMA_ZONE_NODUMP
|
|
|
|
Pages belonging to the zone will not be included into mini-dumps.
|
2013-04-08 19:10:45 +00:00
|
|
|
.It Dv UMA_ZONE_PCPU
|
|
|
|
An allocation from zone would have
|
|
|
|
.Va mp_ncpu
|
|
|
|
shadow copies, that are privately assigned to CPUs.
|
|
|
|
A CPU can address its private copy using base allocation address plus
|
|
|
|
multiple of current CPU id and
|
|
|
|
.Fn sizeof "struct pcpu" :
|
|
|
|
.Bd -literal -offset indent
|
|
|
|
foo_zone = uma_zcreate(..., UMA_ZONE_PCPU);
|
|
|
|
...
|
|
|
|
foo_base = uma_zalloc(foo_zone, ...);
|
|
|
|
...
|
|
|
|
critical_enter();
|
|
|
|
foo_pcpu = (foo_t *)zpcpu_get(foo_base);
|
|
|
|
/* do something with foo_pcpu */
|
|
|
|
critical_exit();
|
|
|
|
.Ed
|
2013-03-21 16:19:46 +00:00
|
|
|
.It Dv UMA_ZONE_OFFPAGE
|
|
|
|
By default book-keeping of items within a slab is done in the slab page itself.
|
|
|
|
This flag explicitly tells subsystem that book-keeping structure should be
|
|
|
|
allocated separately from special internal zone.
|
|
|
|
This flag requires either
|
|
|
|
.Dv UMA_ZONE_VTOSLAB
|
|
|
|
or
|
|
|
|
.Dv UMA_ZONE_HASH ,
|
|
|
|
since subsystem requires a mechanism to find a book-keeping structure
|
2016-05-01 22:00:41 +00:00
|
|
|
to an item being freed.
|
2013-03-21 16:19:46 +00:00
|
|
|
The subsystem may choose to prefer offpage book-keeping for certain zones
|
|
|
|
implicitly.
|
|
|
|
.It Dv UMA_ZONE_ZINIT
|
|
|
|
The zone will have its
|
|
|
|
.Ft uma_init
|
|
|
|
method set to internal method that initializes a new allocated slab
|
|
|
|
to all zeros.
|
2013-04-11 18:46:41 +00:00
|
|
|
Do not mistake
|
2013-03-21 16:19:46 +00:00
|
|
|
.Ft uma_init
|
|
|
|
method with
|
|
|
|
.Ft uma_ctor .
|
|
|
|
A zone with
|
|
|
|
.Dv UMA_ZONE_ZINIT
|
|
|
|
flag would not return zeroed memory on every
|
|
|
|
.Fn uma_zalloc .
|
|
|
|
.It Dv UMA_ZONE_HASH
|
|
|
|
The zone should use an internal hash table to find slab book-keeping
|
|
|
|
structure where an allocation being freed belongs to.
|
|
|
|
.It Dv UMA_ZONE_VTOSLAB
|
|
|
|
The zone should use special field of
|
|
|
|
.Vt vm_page_t
|
|
|
|
to find slab book-keeping structure where an allocation being freed belongs to.
|
|
|
|
.It Dv UMA_ZONE_MALLOC
|
|
|
|
The zone is for the
|
|
|
|
.Xr malloc 9
|
|
|
|
subsystem.
|
|
|
|
.It Dv UMA_ZONE_VM
|
|
|
|
The zone is for the VM subsystem.
|
2018-03-24 23:58:44 +00:00
|
|
|
.It Dv UMA_ZONE_NUMA
|
|
|
|
The zone should use a first-touch NUMA policy rather than the round-robin
|
|
|
|
default. Callers that do not free memory on the same domain it is allocated
|
|
|
|
from will cause mixing in per-cpu caches. See
|
|
|
|
.Xr numa 9 for more details.
|
2013-03-21 16:19:46 +00:00
|
|
|
.El
|
|
|
|
.Pp
|
2001-01-27 19:13:08 +00:00
|
|
|
To allocate an item from a zone, simply call
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zalloc
|
2002-04-30 14:26:22 +00:00
|
|
|
with a pointer to that zone
|
|
|
|
and set the
|
2002-04-30 16:30:19 +00:00
|
|
|
.Fa flags
|
|
|
|
argument to selected flags as documented in
|
|
|
|
.Xr malloc 9 .
|
2002-04-30 14:26:22 +00:00
|
|
|
It will return a pointer to an item if successful,
|
|
|
|
or
|
2001-01-27 19:13:08 +00:00
|
|
|
.Dv NULL
|
|
|
|
in the rare case where all items in the zone are in use and the
|
2002-04-30 14:26:22 +00:00
|
|
|
allocator is unable to grow the zone
|
2012-10-28 21:01:32 +00:00
|
|
|
and
|
2002-04-30 14:26:22 +00:00
|
|
|
.Dv M_NOWAIT
|
|
|
|
is specified.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Pp
|
|
|
|
Items are released back to the zone from which they were allocated by
|
|
|
|
calling
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zfree
|
2001-01-27 19:13:08 +00:00
|
|
|
with a pointer to the zone and a pointer to the item.
|
2010-10-19 16:06:00 +00:00
|
|
|
If
|
|
|
|
.Fa item
|
|
|
|
is
|
|
|
|
.Dv NULL ,
|
|
|
|
then
|
|
|
|
.Fn uma_zfree
|
|
|
|
does nothing.
|
2001-08-09 16:01:27 +00:00
|
|
|
.Pp
|
2008-06-19 18:33:38 +00:00
|
|
|
The variations
|
|
|
|
.Fn uma_zalloc_arg
|
|
|
|
and
|
|
|
|
.Fn uma_zfree_arg
|
2018-03-24 23:58:44 +00:00
|
|
|
allow callers to
|
2008-06-19 18:33:38 +00:00
|
|
|
specify an argument for the
|
|
|
|
.Dv ctor
|
|
|
|
and
|
|
|
|
.Dv dtor
|
|
|
|
functions, respectively.
|
2018-03-24 23:58:44 +00:00
|
|
|
The
|
|
|
|
.Fn uma_zalloc_domain
|
|
|
|
function allows callers to specify a fixed
|
|
|
|
.Xr numa 9 domain to allocate from. This uses a guaranteed but slow path in
|
|
|
|
the allocator which reduces concurrency. The
|
|
|
|
.Fn uma_zfree_domain
|
|
|
|
function should be used to return memory allocated in this fashion. This
|
|
|
|
function infers the domain from the pointer and does not require it as an
|
|
|
|
argument.
|
2008-06-19 18:33:38 +00:00
|
|
|
.Pp
|
2002-04-30 15:04:41 +00:00
|
|
|
Created zones,
|
|
|
|
which are empty,
|
2001-08-09 16:01:27 +00:00
|
|
|
can be destroyed using
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zdestroy ,
|
2001-08-09 16:01:27 +00:00
|
|
|
freeing all memory that was allocated for the zone.
|
|
|
|
All items allocated from the zone with
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zalloc
|
2001-08-09 16:01:27 +00:00
|
|
|
must have been freed with
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zfree
|
2001-08-09 16:01:27 +00:00
|
|
|
before.
|
2003-07-21 14:20:58 +00:00
|
|
|
.Pp
|
2010-10-16 04:14:45 +00:00
|
|
|
The
|
2003-07-21 14:20:58 +00:00
|
|
|
.Fn uma_zone_set_max
|
2010-10-16 04:14:45 +00:00
|
|
|
function limits the number of items
|
|
|
|
.Pq and therefore memory
|
|
|
|
that can be allocated to
|
|
|
|
.Fa zone .
|
2003-07-21 14:20:58 +00:00
|
|
|
The
|
|
|
|
.Fa nitems
|
2010-10-16 04:14:45 +00:00
|
|
|
argument specifies the requested upper limit number of items.
|
2010-10-16 04:41:45 +00:00
|
|
|
The effective limit is returned to the caller, as it may end up being higher
|
|
|
|
than requested due to the implementation rounding up to ensure all memory pages
|
|
|
|
allocated to the zone are utilised to capacity.
|
2010-10-16 04:14:45 +00:00
|
|
|
The limit applies to the total number of items in the zone, which includes
|
2003-07-21 14:20:58 +00:00
|
|
|
allocated items, free items and free items in the per-cpu caches.
|
|
|
|
On systems with more than one CPU it may not be possible to allocate
|
|
|
|
the specified number of items even when there is no shortage of memory,
|
|
|
|
because all of the remaining free items may be in the caches of the
|
|
|
|
other CPUs when the limit is hit.
|
2010-10-16 04:14:45 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fn uma_zone_get_max
|
|
|
|
function returns the effective upper limit number of items for a zone.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fn uma_zone_get_cur
|
|
|
|
function returns the approximate current occupancy of the zone.
|
|
|
|
The returned value is approximate because appropriate synchronisation to
|
2012-02-25 14:31:25 +00:00
|
|
|
determine an exact value is not performed by the implementation.
|
2010-10-16 04:14:45 +00:00
|
|
|
This ensures low overhead at the expense of potentially stale data being used
|
|
|
|
in the calculation.
|
2012-12-07 22:27:13 +00:00
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fn uma_zone_set_warning
|
|
|
|
function sets a warning that will be printed on the system console when the
|
|
|
|
given zone becomes full and fails to allocate an item.
|
2015-12-20 02:05:33 +00:00
|
|
|
The warning will be printed no more often than every five minutes.
|
2012-12-07 22:27:13 +00:00
|
|
|
Warnings can be turned off globally by setting the
|
|
|
|
.Va vm.zone_warnings
|
|
|
|
sysctl tunable to
|
|
|
|
.Va 0 .
|
2014-02-07 14:29:03 +00:00
|
|
|
.Pp
|
|
|
|
The
|
2015-12-20 02:05:33 +00:00
|
|
|
.Fn uma_zone_set_maxaction
|
|
|
|
function sets a function that will be called when the given zone becomes full
|
|
|
|
and fails to allocate an item.
|
2016-06-08 09:19:47 +00:00
|
|
|
The function will be called with the zone locked.
|
|
|
|
Also, the function
|
|
|
|
that called the allocation function may have held additional locks.
|
|
|
|
Therefore,
|
2015-12-20 02:05:33 +00:00
|
|
|
this function should do very little work (similar to a signal handler).
|
|
|
|
.Pp
|
|
|
|
The
|
2014-02-07 14:29:03 +00:00
|
|
|
.Fn SYSCTL_UMA_MAX parent nbr name access zone descr
|
|
|
|
macro declares a static
|
|
|
|
.Xr sysctl
|
|
|
|
oid that exports the effective upper limit number of items for a zone.
|
|
|
|
The
|
|
|
|
.Fa zone
|
|
|
|
argument should be a pointer to
|
|
|
|
.Vt uma_zone_t .
|
|
|
|
A read of the oid returns value obtained through
|
|
|
|
.Fn uma_zone_get_max .
|
|
|
|
A write to the oid sets new value via
|
|
|
|
.Fn uma_zone_set_max .
|
|
|
|
The
|
|
|
|
.Fn SYSCTL_ADD_UMA_MAX ctx parent nbr name access zone descr
|
|
|
|
macro is provided to create this type of oid dynamically.
|
|
|
|
.Pp
|
|
|
|
The
|
|
|
|
.Fn SYSCTL_UMA_CUR parent nbr name access zone descr
|
2016-01-16 00:37:27 +00:00
|
|
|
macro declares a static read-only
|
2014-02-07 14:29:03 +00:00
|
|
|
.Xr sysctl
|
|
|
|
oid that exports the approximate current occupancy of the zone.
|
|
|
|
The
|
|
|
|
.Fa zone
|
2014-12-21 10:57:42 +00:00
|
|
|
argument should be a pointer to
|
2014-02-07 14:29:03 +00:00
|
|
|
.Vt uma_zone_t .
|
|
|
|
A read of the oid returns value obtained through
|
|
|
|
.Fn uma_zone_get_cur .
|
|
|
|
The
|
|
|
|
.Fn SYSCTL_ADD_UMA_CUR ctx parent nbr name zone descr
|
|
|
|
macro is provided to create this type of oid dynamically.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Sh RETURN VALUES
|
|
|
|
The
|
2002-04-30 12:45:31 +00:00
|
|
|
.Fn uma_zalloc
|
2001-01-27 19:13:08 +00:00
|
|
|
function returns a pointer to an item, or
|
|
|
|
.Dv NULL
|
2012-10-28 21:01:32 +00:00
|
|
|
if the zone ran out of unused items
|
|
|
|
and
|
|
|
|
.Dv M_NOWAIT
|
|
|
|
was specified.
|
Make UMA and malloc(9) return non-executable memory in most cases.
Most kernel memory that is allocated after boot does not need to be
executable. There are a few exceptions. For example, kernel modules
do need executable memory, but they don't use UMA or malloc(9). The
BPF JIT compiler also needs executable memory and did use malloc(9)
until r317072.
(Note that a side effect of r316767 was that the "small allocation"
path in UMA on amd64 already returned non-executable memory. This
meant that some calls to malloc(9) or the UMA zone(9) allocator could
return executable memory, while others could return non-executable
memory. This change makes the behavior consistent.)
This change makes malloc(9) return non-executable memory unless the new
M_EXEC flag is specified. After this change, the UMA zone(9) allocator
will always return non-executable memory, and a KASSERT will catch
attempts to use the M_EXEC flag to allocate executable memory using
uma_zalloc() or its variants.
Allocations that do need executable memory have various choices. They
may use the M_EXEC flag to malloc(9), or they may use a different VM
interfact to obtain executable pages.
Now that malloc(9) again allows executable allocations, this change also
reverts most of r317072.
PR: 228927
Reviewed by: alc, kib, markj, jhb (previous version)
Sponsored by: Netflix
Differential Revision: https://reviews.freebsd.org/D15691
2018-06-13 17:04:41 +00:00
|
|
|
.Sh IMPLEMENTATION NOTES
|
|
|
|
The memory that these allocation calls return is not executable.
|
|
|
|
The
|
|
|
|
.Fn uma_zalloc
|
|
|
|
function does not support the
|
|
|
|
.Dv M_EXEC
|
|
|
|
flag to allocate executable memory.
|
|
|
|
Not all platforms enforce a distinction between executable and
|
|
|
|
non-executable memory.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Sh SEE ALSO
|
|
|
|
.Xr malloc 9
|
|
|
|
.Sh HISTORY
|
|
|
|
The zone allocator first appeared in
|
|
|
|
.Fx 3.0 .
|
2002-04-30 14:56:44 +00:00
|
|
|
It was radically changed in
|
|
|
|
.Fx 5.0
|
|
|
|
to function as a slab allocator.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Sh AUTHORS
|
|
|
|
.An -nosplit
|
|
|
|
The zone allocator was written by
|
|
|
|
.An John S. Dyson .
|
2002-04-30 14:56:44 +00:00
|
|
|
The zone allocator was rewritten in large parts by
|
2014-06-26 21:44:30 +00:00
|
|
|
.An Jeff Roberson Aq Mt jeff@FreeBSD.org
|
2002-04-30 14:56:44 +00:00
|
|
|
to function as a slab allocator.
|
2001-01-27 19:13:08 +00:00
|
|
|
.Pp
|
|
|
|
This manual page was written by
|
2014-06-26 21:44:30 +00:00
|
|
|
.An Dag-Erling Sm\(/orgrav Aq Mt des@FreeBSD.org .
|
2002-04-30 14:56:44 +00:00
|
|
|
Changes for UMA by
|
2014-06-26 21:44:30 +00:00
|
|
|
.An Jeroen Ruigrok van der Werven Aq Mt asmodai@FreeBSD.org .
|