generated from erix/meta
[FEATURE] Share allocation within caller-owned memory regions #1
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-owned-region#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and motivation
Kernel's region allocator should be reusable by native tools without copying
its implementation or adding implicit memory acquisition.
Proposed behavior and scope
Share the existing free-list algorithm and add a serialized
GlobalAllocadapter. Each caller supplies one writable region and keeps its original owner.
Migrate Kernel to the shared primitive without changing its reserved-heap policy.
Authority, security and reliability
Installation is explicit and one-shot. Allocation cannot discover services,
acquire backing, grow the region or select a fallback. Unsafe callers preserve
exclusive access, mapping lifetime and exact pointer/layout pairs. Local drain
observations do not retire native mappings or grants; uncertain cleanup keeps
those owners alive. Allocation failure records scalar state without allocating.
Acceptance criteria
Alternatives and tradeoffs
Keeping separate copies makes fixes diverge. A growing heap would require a
separate memory-acquisition policy; it is outside this library's boundary.
The serialization guard excludes reentry and promises no scheduler fairness.
Tracking and rollout
Supports native build tools
and phase completion.
Register the actual template seed, publish the library with a registered CI
helper, then migrate Kernel and refresh the final dependency snapshots.
Native startup and authenticated tool bindings remain separate work.
Review: shared allocation implementation.