Adding support for shared_memory allocator for multiprocessing.

Open
#107 0 comments 0 reactions 0 assignees View on GitHub

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
c, python
Domain
backend

Research direction

Start with the static map_alloc and dealloc functions named in the issue, then trace the constructor path and its buffer handling. Compare the proposed SharedMemory.buf use with the existing Numpy approach, including the C extension boundary. Done should be a clearly scoped design and feasibility result with any required tests identified.

Written by the indexing model from the issue text.

Description

How feasible is it modifying static MapObject * map_alloc(void) (and the ...dealloc functions) to use a custom allocator, if buffer parameter is passed to constructor, so a multiprocessing.shared_memory.SharedMemory().buf can be used, similarly to Numpy?

Dominant language
C
Stars
1.2k
Forks
60
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MagicStack/immutables

All issues in MagicStack/immutables

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.