Lines Matching refs:that

9 - the VM subsystem that provides allocations at the granularity of pages (with
14 In addition to that, `<kern/kalloc.h>` provides a variable-size general purpose
24 - `<kern/zalloc_internal.h>` for interfaces that need to be exported
33 The kernel sometimes needs to provide persistent allocations that depend on
34 parameters that aren't compile time constants, but will not vary over time (NCPU
37 The zone subsystem provides a `zalloc_permanent*` family of functions that help
51 - `Z_WAITOK` means that the zone allocator can wait and block,
61   be zeroed regardless, but it's always clearer to specify it), note that it is
64 - `Z_NOFAIL` if the caller knows the allocation can't fail: allocations that are
68   `Z_NOFAIL` can be used to denote that the caller knows about this.
98 memory that doesn't contain pointers is using the data API `kalloc_data` or
102 Note that at this time, those interfaces aren't exported to third parties,
107 The typed allocators assume that allocated types fit a very precise model.
120 Do note that `__kernel_data_semantics` and `__kernel_dual_semantics`
130   we have typically found that there is a large array of data,
131   or some buffer in that type, the solution is to outline this allocation.
157 When allocating untyped memory with the data APIs ensure that it doesn't
159 consider splitting the allocation into two: one part that is typed and contains
160 the kernel pointers and the second that is untyped and data-only.
213       Note that this is absolutely OK to use this variant
242       Note that this is absolutely OK to use this variant
275 with -fbounds-safety semantics. Please note that arguments are evaluated
294 `operator delete` are injected that force objects to enroll into `kalloc_type`.
296 Note that idiomatic IOKit is supposed to use `OSTypeAlloc(Class)`.
356 data that we prefer to be known by the owning object