Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
darshan
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 73
    • Issues 73
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 5
    • Merge Requests 5
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • darshan
  • darshan
  • Issues
  • #161

Closed
Open
Opened Sep 24, 2015 by Shane Snyder@ssnyder
  • Report abuse
  • New issue
Report abuse New issue

detect underlying I/O sizes used by the stream interfaces

Darshan catches fread() and fwrite(), but not the underlying read() and write() calls that occur after buffering.

Assignee
Assign to
triage-feature-request
Milestone
triage-feature-request
Assign milestone
Time tracking
None
Due date
None
2
Labels
enhancement wrapper libraries
Assign labels
  • View project labels
Reference: darshan/darshan#161