CUfilePerGpuStats(3)
π CUfilePerGpuStats(3) π
okay so welcome to the CUfilePerGpuStats(3) page, straight out of the Library Functions Manual bestie β this is the whole vibe, we're doing per-GPU statistics today and we're doing them thoroughly π«Ά
πΈ NAME πΈ
CUfilePerGpuStats β the per-GPU statistics structure used in Level 3. that's the whole pitch, no notes, she said what she said π
β¨ SYNOPSIS β¨
#include <cufile.h>
π Data Fields π
get comfy, there's a lot of them, and yes we're listing every single one because we don't skip π
uint64_t n_dr_readsuint64_t n_dr_writesuint64_t n_inline_regionsuint64_t n_mmapuint64_t n_mmap_erruint64_t n_mmap_freeuint64_t n_mmap_okuint64_t n_nvfs_readsuint64_t n_nvfs_writesuint64_t n_p2p_readsuint64_t n_p2p_writesuint64_t n_posix_readsuint64_t n_posix_writesuint64_t n_reads_erruint64_t n_sparse_regionsuint64_t n_total_readsuint64_t n_total_writesuint64_t n_unaligned_readsuint64_t n_unaligned_writesuint64_t n_writes_erruint64_t read_bw_bytes_per_secuint64_t read_bytesuint64_t read_duration_usuint64_t read_utilizationuint64_t reg_byteschar uuid [16]uint64_t write_bw_bytes_per_secuint64_t write_duration_usuint64_t write_utilizationuint64_t writes_bytes
thirty fields. thirty. she's an overachiever and honestly? obsessed π₯
π¦ DETAILED DESCRIPTION π¦
Per-GPU statistics structure used in Level 3. that's the official description, word for word, and it's giving "confident but mysterious" β the main character energy of documentation ngl π
π FIELD DOCUMENTATION π
okay so here's the part where the page goes through every field one by one. and the notes for each one? literally nothing else. she lists the field, she moves on. minimalism. we respect it π
uint64_t CUfilePerGpuStats::n_dr_reads
uint64_t CUfilePerGpuStats::n_dr_writes
uint64_t CUfilePerGpuStats::n_inline_regions
uint64_t CUfilePerGpuStats::n_mmap
uint64_t CUfilePerGpuStats::n_mmap_err
uint64_t CUfilePerGpuStats::n_mmap_free
uint64_t CUfilePerGpuStats::n_mmap_ok
uint64_t CUfilePerGpuStats::n_nvfs_reads
uint64_t CUfilePerGpuStats::n_nvfs_writes
uint64_t CUfilePerGpuStats::n_p2p_reads
uint64_t CUfilePerGpuStats::n_p2p_writes
uint64_t CUfilePerGpuStats::n_posix_reads
uint64_t CUfilePerGpuStats::n_posix_writes
uint64_t CUfilePerGpuStats::n_reads_err
uint64_t CUfilePerGpuStats::n_sparse_regions
uint64_t CUfilePerGpuStats::n_total_reads
uint64_t CUfilePerGpuStats::n_total_writes
uint64_t CUfilePerGpuStats::n_unaligned_reads
uint64_t CUfilePerGpuStats::n_unaligned_writes
uint64_t CUfilePerGpuStats::n_writes_err
uint64_t CUfilePerGpuStats::read_bw_bytes_per_sec
uint64_t CUfilePerGpuStats::read_bytes
uint64_t CUfilePerGpuStats::read_duration_us
uint64_t CUfilePerGpuStats::read_utilization
uint64_t CUfilePerGpuStats::reg_bytes
char CUfilePerGpuStats::uuid[16]
(yeah, this one's a char array of 16, not a uint64_t β she's different, she's special, we love her π)
uint64_t CUfilePerGpuStats::write_bw_bytes_per_sec
uint64_t CUfilePerGpuStats::write_duration_us
uint64_t CUfilePerGpuStats::write_utilization
uint64_t CUfilePerGpuStats::writes_bytes
real talk bestie: the page doesn't give descriptions beyond the field signatures above, so i'm not gonna sit here and make stuff up about them. what you see is what the docs say, periodt π
π§ AUTHOR π§
Generated automatically by Doxygen for GPUDirect Storage from the source code. no human wrote this, a machine did, and honestly it ate π€β¨
and that's the page!! mwah π«Ά GPUDirect Storage, dated Fri Aug 28 2026, CUfilePerGpuStats(3), that's the source and the date, we're done here, go read your stats bestie ππΈ
π¦ where this page comes from
- arch rolling: cuda 13.4.3-1 Β· LicenseRef-NVIDIA-CUDA
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms