IPA LOCAL MEMORY(9)

💅 IPA Local Memory 💅

okay so welcome to the Kernel API Manual — this is section 9, the IPA Local Memory page, bestie. 💖

The IPA has a block of shared memory, divided into regions used for specific purposes. Slay. ✨

Each region inside that shared block is bounded by an offset (relative to the "ipa-shared" memory range) and a size found in the IPA_SHARED_MEM_SIZE register. 🎀

Each region is optionally preceded by one or more 32-bit "canary" values. These are meant to detect out-of-range writes (if they become corrupted). A given region (such as a filter or routing table) has the same number of canaries for all IPA hardware versions. Still, the number used is defined in the config data, allowing for generic handling of regions. 🦋

The set of memory regions is defined in configuration data. They are subject to these constraints:

• a zero offset and zero size represents an undefined region
• a region’s size does not include space for its "canary" values
• a region’s offset is defined to be past all "canary" values
• offset must be large enough to account for all canaries
• a region’s size may be zero, but may still have canaries
• all offsets must be 8-byte aligned
• most sizes must be a multiple of 8
• modem memory size must be a multiple of 4
• the microcontroller ring offset must be a multiple of 1024

no cap, those constraints are the rules — not a suggestion, bestie 💀

🌈 SEE ALSO 🌈

• Kernel file ./drivers/net/ipa/ipa_mem.h
• struct ipa_mem(9)

and that’s the whole vibe! this page came from source/version ./drivers/net/ipa and is dated October 2026 — mwah, bye bestie! 💜🎀