pavel-kirienko/o1heap
Constant-complexity, deterministic, very fast memory allocator (heap) for hard real-time high-integrity embedded systems. Allocation takes ≈120 cycles @ RP2350 irrespective of heap usage. There is little activity because the project is finished and does not require further changes.
Topics
Explore related topics
Jump into the topic listings this repository belongs to.
Join the conversation
Reviews · Questions · Posts
Share what you know about o1heap — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Write or update your review
Explain what worked, what broke down, and what another team should know before adopting o1heap.
Project Q&A
Questions and answers
Browse implementation threads tied directly to pavel-kirienko/o1heap. Each question links through to the full answer page.
Be the first to ask how teams run o1heap in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
Posts tagged with the same topics
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses o1heap — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post