OpenDevicePartnership / OpenDevicePartnership/patina
[Feature]: Merge GCD and Allocator Modules
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 544
- Forks
- 54
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 30
Description
Feature Overview
Today the GCD and allocator modules are distinct, although they are part of the same larger component (perhaps called Memory Manager). This is mostly an artifact of the fact that the allocator existed before the GCD.
By having these as distinct modules, it creates coupled interfaces between the two and the need for callbacks to be piped through to interact with the top level dxe_core interfaces.
Solution Overview
These two modules can be combined into a memory_manager crate that has the functionality of both.
Alternatives Considered
No response
Urgency
Low
Are you going to implement the feature request?
None
Do you need maintainer feedback?
None
Anything else?
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing GCD and allocator modules and tracing the interfaces and callbacks between them and the top-level dxe_core interfaces. Define the boundaries of a combined memory_manager crate and verify that both modules' functionality remains available without the coupled interfaces. Done means the two modules are merged and the callback plumbing is removed or consolidated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100