drivers/net/ethernet/intel/iavf/iavf_osdep.h
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/intel/iavf/iavf_osdep.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/intel/iavf/iavf_osdep.h- Extension
.h- Size
- 1161 bytes
- Lines
- 47
- Domain
- Driver Families
- Bucket
- drivers/net
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.hlinux/if_ether.hlinux/if_vlan.hlinux/tcp.hlinux/pci.hlinux/io-64-nonatomic-lo-hi.h
Detected Declarations
struct iavf_dma_memstruct iavf_virt_mem
Annotated Snippet
struct iavf_dma_mem {
void *va;
dma_addr_t pa;
u32 size;
};
#define iavf_allocate_dma_mem(h, m, unused, s, a) \
iavf_allocate_dma_mem_d(h, m, s, a)
struct iavf_virt_mem {
void *va;
u32 size;
};
#define iavf_debug(h, m, s, ...) \
do { \
if (((m) & (h)->debug_mask)) \
pr_info("iavf %02x:%02x.%x " s, \
(h)->bus.bus_id, (h)->bus.device, \
(h)->bus.func, ##__VA_ARGS__); \
} while (0)
#endif /* _IAVF_OSDEP_H_ */
Annotation
- Immediate include surface: `linux/types.h`, `linux/if_ether.h`, `linux/if_vlan.h`, `linux/tcp.h`, `linux/pci.h`, `linux/io-64-nonatomic-lo-hi.h`.
- Detected declarations: `struct iavf_dma_mem`, `struct iavf_virt_mem`.
- Atlas domain: Driver Families / drivers/net.
- 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.