Custom IO communicator instead of stride

Open
#1,590 2 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
Domain
distributed-systems

Research direction

Start by tracing IOSystem creation and how the MPI stride selects the I/O processes. Determine the API and implementation changes needed to accept a subset communicator for non-round-robin mappings, then verify that the communicator is restricted to the calculating communicator and that custom mappings work as intended.

Written by the indexing model from the issue text.

Description

enhancement

When creating an IOSystem one passes an MPI stride.

However, why not let the programmer pass a subset communicator to allow custom strides (say if the mapping isn't round-robin)?

The only requirement is that the communicator is a subset of the calculating communicator.

Dominant language
C
Stars
160
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 NCAR/ParallelIO

All issues in NCAR/ParallelIO

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.