VM_MAP_MADVISE(9)

✨ NAME ✨

okay bestie, meet vm_map_madvise — apply advice about use of memory to map entries. This is vm_map_madvise(9), aka VM_MAP_MADVISE(9), from the Kernel Developer's Manual, and it's literally here to pass vibes about memory along to map entries. 💖

🌸 SYNOPSIS 🌸

#include <sys/param.h>
#include <vm/vm.h>
#include <vm/vm_map.h>

int
vm_map_madvise(vm_map_t map, vm_offset_t start, vm_offset_t end,
    int behav);

💅 DESCRIPTION 💅

So the vm_map_madvise() function applies the flags behav to the entries within map between start and end. Periodt.

Advisories are classified as either those affecting the vm_map_entry structure, or those affecting the underlying objects. iykyk — it's giving two whole categories of advice.

The vm_map_madvise() function is used by the madvise(2) system call. so if you've ever called madvise(2), this is the kernel-side bestie doing the work.

🫶 RETURN VALUES 🫶

The vm_map_madvise() function returns 0 if successful. If the behav argument was not recognised, KERN_INVALID_ARGUMENT is returned. No cap, that's the whole return tea.

👑 SEE ALSO 👑

• madvise(2)
• vm_map(9)

🎀 AUTHORS 🎀

This manual page was written by Bruce M Simpson <bms@spc.org>. slay, Bruce.

okay bye bestie, this page is from Debian, dated July 19, 2003 💖✨