fs/xfs/libxfs/xfs_bit.h
Source file repositories/reference/linux-study-clean/fs/xfs/libxfs/xfs_bit.h
File Facts
- System
- Linux kernel
- Corpus path
fs/xfs/libxfs/xfs_bit.h- Extension
.h- Size
- 1577 bytes
- Lines
- 76
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
function Copyrightfunction xfs_mask32lofunction xfs_mask64lofunction xfs_highbit32function xfs_highbit64function xfs_lowbit32function xfs_lowbit64
Annotated Snippet
if (w) {
n = ffs(w);
if (n)
n += 32;
}
}
return n - 1;
}
/* Return whether bitmap is empty (1 == empty) */
extern int xfs_bitmap_empty(uint *map, uint size);
/* Count continuous one bits in map starting with start_bit */
extern int xfs_contig_bits(uint *map, uint size, uint start_bit);
/* Find next set bit in map */
extern int xfs_next_bit(uint *map, uint size, uint start_bit);
#endif /* __XFS_BIT_H__ */
Annotation
- Detected declarations: `function Copyright`, `function xfs_mask32lo`, `function xfs_mask64lo`, `function xfs_highbit32`, `function xfs_highbit64`, `function xfs_lowbit32`, `function xfs_lowbit64`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.