O_DIRECT support for dtar

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
cli, performance

Research direction

Start by comparing how dtar handles archive creation and extraction with the existing O_DIRECT support in dsync and dcp. Determine the option’s expected behavior for large archives containing large files, then verify that dtar supports O_DIRECT consistently for both relevant operations.

Written by the indexing model from the issue text.

Description

it would dtar supports O_DIRECT optoin as dsync and dcp does.
it doesn't make sense for many small files in the archive file, but I believe O_DIRECT in dtar is still useful when it extract/archive for a very large archive file which contains many large files (e.g. millions of 2MB image file).

Dominant language
C
Stars
200
Forks
85
Avg merge
3d 21h
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

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 hpc/mpifileutils

All issues in hpc/mpifileutils

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.