STRUCT IOMMU_DIRTY_BITMAP(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct iommu_dirty_bitmap(9) πŸ’–

okay so bestie, this is a page from the Kernel API Manual and it's literally just the shape of one struct β€” a little two-field bundle of joy that keeps track of dirty IOVA bitmap state. no cap, that's the whole vibe. it's giving "small but crucial" and we're obsessed πŸŽ€


✨ NAME ✨

struct iommu_dirty_bitmap β€” Dirty IOVA bitmap state πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

struct iommu_dirty_bitmap {
    struct iova_bitmap *bitmap;
    struct iommu_iotlb_gather *gather;
};

look at her. two pointers, zero drama, main character energy ✨


🌸 Members 🌸

so there's exactly two members and each one is doing its own iconic thing:

  • bitmap β€” the IOVA bitmap, periodt. that's the actual dirty-tracking bitmap living in this struct πŸ—ΊοΈ
  • gather β€” range information for a pending IOTLB flush πŸ”₯ like, the scoop on which range still needs flushing. it's not flushed yet, it's pending, iykyk.
ngl both of these are pointers, so this struct is lowkey just a cute little pair of references holding hands 🫢

πŸ‘‘ SEE ALSO πŸ‘‘

bestie, the cross-reference section is stacked. like, genuinely a whole friend group. every single one of these, no skipping πŸ™ˆ


okay that's the whole page, you ate that πŸ’…βœ¨ this one lives in ./include/linux and it's dated October 2026 β€” so yeah, hydrating, staying informed, reading your kernel headers. slay πŸ§šπŸ’œ

πŸ“¦ where this page comes from