Lines Matching refs:kalloc

14 In addition to that, `<kern/kalloc.h>` provides a variable-size general purpose
21 - `<kern/zalloc.h>` and `<kern/kalloc.h>` for its API surface, which most
48 3. In general we prefer zalloc or kalloc interfaces, and would like to abandon
55 For all `kalloc` or `kheap_alloc` variants, these advices apply:
89 `zalloc` and `kalloc` are considered the primitive allocation interfaces which
120       This is the true core implementation of `kalloc`, see documentation about
121       kalloc heaps.
125     <th>kalloc</th>
130       In XNU, `kalloc` is equivalent to `kheap_alloc(KHEAP_DEFAULT)`.
132       In kernel extensions, `kalloc` is equivalent to `kheap_alloc(KHEAP_KEXT)`.
148       `IOMalloc` is a straight wrapper around `kalloc` and behaves like
149       `kalloc`. It does provide some debugging features integrated with `IOKit`
154       should use the primitive `zalloc` or `kalloc` directly.
164       It redirects to the `KHEAP_KEXT` kalloc heap as there is no use of C++
180       This is a legacy BSD interface that functions mostly like `kalloc`.
270 behavior of `zalloc` and `kalloc`:
281 true of `kalloc` when the allocation is served by the VM.
333 ability to create a zone rather than being allocated in a kalloc heap.
360 element: when using the `Z_ZERO` (resp. `M_ZERO`) with `zalloc` or `kalloc`
403 similar fashion to `kalloc`. These functions will never fail (if the allocation
408 ## kalloc: a heap of zones
416 The kernel calls the collection of zones that back kalloc a "kalloc heap", and
419 - `KHEAP_DEFAULT`, the "default" heap, is the one that serves `kalloc` in Core
421 - `KHEAP_KEXT`, the kernel extension heap, is the one that serves `kalloc` in
440 to define zone views and kalloc heap aliases, which are two similar concepts for
441 zones and kalloc heaps respectively.
445 another regular zone, or a specific zone of a kalloc heap. This is for example
451 to declare a kalloc heap alias that gets its own accounting. It is particularly