llnl / llnl/UnifyFS

Making headers and source public for tools within Unifyfs.

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

Nobody has claimed this yet.

enhancement
Dominant language
C
Stars
122
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Describe the problem you're observing

Currently, unifyfs supports several tools such as transferring data from pfs to unifyfs. These tools are extremely useful but there is no programmatic way to use these tools.

It would be great if we could expose a lib of these tools by extracting the main logical pieces and expose their header for including in any application.

Currently, I copy the transfer utility code into my repository and include it to perform prefetching from pfs to unifyfs.

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.

Research direction

Start by locating the existing transfer utility code, especially the logic used for prefetching from PFS to UnifyFS. Identify which pieces could form a reusable library and which headers would need to be public; done means applications can call these tools programmatically without copying the utility code.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.