memblock_va...uma_coverage(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… memblock_validate_numa_coverage(9) πŸ’…

okay so welcome to the Kernel API Manual bestie, this is the page for memblock_validate_numa_coverage and honestly? she's a vibe check for your firmware 🫢


✨ NAME ✨

memblock_validate_numa_coverage β€” the girl who checks whether the amount of memory chillin' with no node ID assigned is under a threshold πŸŽ€


🌸 SYNOPSIS 🌸

bool __init_memblock memblock_validate_numa_coverage (unsigned long
threshold_bytes );

πŸ’– ARGUMENTS πŸ’–

  • threshold_bytes β€” the maximal memory size that's allowed to have an unassigned node ID, measured in bytes. like, the absolute most memory that can be ~homeless~ before she starts side-eyeing πŸ‘€

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea β˜• β€” a buggy firmware may report memory that does not belong to any node. rude, honestly. 😭

she checks if the amount of that unassigned-node memory is below threshold_bytes, and that's literally it. simple, iconic, no notes ✨


⭐ RETURN ⭐

  • true on success πŸ’š
  • false on failure πŸ’€

🌈 SEE ALSO 🌈

the whole memblock friend group showed up, no cap:


πŸ’… and that's the whole page, periodt πŸ’…

shoutout to ./mm for being the source, the manual version being October 2026, and the page answering to the name memblock_va...uma_coverage(9) β€” mwah, catch you in the next manpage bestie πŸ’œπŸŽ€

πŸ“¦ where this page comes from