include/linux/t10-pi.h
Source file repositories/reference/linux-study-clean/include/linux/t10-pi.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/t10-pi.h- Extension
.h- Size
- 1797 bytes
- Lines
- 77
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.hlinux/blk-mq.hlinux/wordpart.h
Detected Declarations
struct t10_pi_tuplestruct crc64_pi_tupleenum t10_dif_typefunction full_pi_ref_tagfunction t10_pi_ref_tagfunction lower_48_bitsfunction ext_pi_ref_tag
Annotated Snippet
struct t10_pi_tuple {
__be16 guard_tag; /* Checksum */
__be16 app_tag; /* Opaque storage */
__be32 ref_tag; /* Target LBA or indirect LBA */
};
#define T10_PI_APP_ESCAPE cpu_to_be16(0xffff)
#define T10_PI_REF_ESCAPE cpu_to_be32(0xffffffff)
static inline u32 t10_pi_ref_tag(struct request *rq)
{
return lower_32_bits(full_pi_ref_tag(rq));
}
struct crc64_pi_tuple {
__be64 guard_tag;
__be16 app_tag;
__u8 ref_tag[6];
};
/**
* lower_48_bits() - return bits 0-47 of a number
* @n: the number we're accessing
*/
static inline u64 lower_48_bits(u64 n)
{
return n & ((1ull << 48) - 1);
}
static inline u64 ext_pi_ref_tag(struct request *rq)
{
return lower_48_bits(full_pi_ref_tag(rq));
}
#endif
Annotation
- Immediate include surface: `linux/types.h`, `linux/blk-mq.h`, `linux/wordpart.h`.
- Detected declarations: `struct t10_pi_tuple`, `struct crc64_pi_tuple`, `enum t10_dif_type`, `function full_pi_ref_tag`, `function t10_pi_ref_tag`, `function lower_48_bits`, `function ext_pi_ref_tag`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.