Support mmap/sbrk interception for avoiding data copies between runtime and client
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems, performance
Research direction
Start by tracing the runtime and client allocation paths involved in copying data, then examine how mmap/sbrk interception and shared memory could fit those paths. Identify where processes would register private allocators and where the runtime would maintain the process-to-allocator mapping. Done means data can avoid copies, registrations are tracked, and a wreaper thread unregisters dead processes.
Written by the indexing model from the issue text.
Description
Currently, we copy data between clients and runtime since the runtime is in a different address space. However, if we intercept mmap/sbrk and put all data in SHM, this will allow applications to avoid the data copy, particularly for GET.
Each process will have to register its private allocator with the runtime. The runtime will have to store a mapping between process ID and allocator.
A well-formed version will have to have a wreaper thread to unregister dead processes automatically.
- Dominant language
- C++
- Stars
- 34
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from HDFGroup/hermes
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Figure is missing on Wiki pageMay be free again @lukemartinlogan claimed this 785 days ago, and no pull request is open. Opendocumentation
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
grumpycoders/pcsx-redux#2667 ·
-
GCC 15.2: -Wcast-qual warning - cast discards const qualifier from pointer target type (H5trace.c)Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
google/tensorstore#305 ·
-
bug module: copilot
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
MaaAssistantArknights/MaaAssistantArknights#19250 · 2 comments ·
Maintainers usually reply within 1 day