ccio_alloc_range(9)

💖 ccio_alloc_range(9) — Kernel API Manual ✨

okay bestie, so this is a page from the Kernel API Manual for ccio_alloc_range — yes the (9) means kernel-section, we love a glow-up 💅. Strap in, it's short but it eats.

🌸 NAME 🌸

ccio_alloc_range — literally allocates pages in the ioc's resource map. that's the whole vibe. ✨

🦋 SYNOPSIS 🦋

int ccio_alloc_range (struct ioc *ioc , struct device *dev , size_t size
);

that's it, that's the whole signature. no cap. 🫶

🎀 ARGUMENTS 🎀

• ioc — The I/O Controller. the main character here, honestly 👑
• dev — The PCI device. hi bestie, welcome to the party 💖
• size — The requested number of bytes to be mapped into the I/O Pdir... (yes the original trail-off with the three dots is canonical, we respect the ellipsis 🙈)

⭐ DESCRIPTION ⭐

So what does this function do? It searches the resource map of the ioc to locate a range of available pages for the requested size. That's it. That's the assignment. It finds you the pages you asked for in the ioc's resource map. lowkey iconic, highkey useful. 🔥

ngl, the manpage gives you exactly this one sentence of behaviour, so don't come at me for more — I'm not out here inventing lore 💀

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/parisc/ccio-dma.c — go read it, iykyk 🧚

and the whole friend group, in this order:

• ccio_free_range(9)
• ccio_io_pdir_entry(9)
• ccio_clear_io_tlb(9)
• ccio_mark_invalid(9)
• ccio_dma_supported(9)
• ccio_map_single(9)
• ccio_unmap_phys(9)
• ccio_alloc(9)
• ccio_free(9)
• ccio_map_sg(9)
• ccio_unmap_sg(9)
• ccio_find_ioc(9)
• ccio_get_iommu(9)
• ccio_ioc_init(9)
• ccio_probe(9)
• ccio_init(9)

---

and that's the page, bestie 💜 it lives at ./drivers/parisc, it's dated October 2026, and it goes by ccio_alloc_range(9) — periodt. go touch some IOMMU 🦋🌸💅