include/uapi/misc/mrvl_cn10k_dpi.h
Source file repositories/reference/linux-study-clean/include/uapi/misc/mrvl_cn10k_dpi.h
File Facts
- System
- Linux kernel
- Corpus path
include/uapi/misc/mrvl_cn10k_dpi.h- Extension
.h- Size
- 972 bytes
- Lines
- 40
- Domain
- Repository Root And Misc
- Bucket
- include
- Inferred role
- Repository Root And Misc: implementation source
- Status
- source implementation candidate
Why This File Exists
Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/types.h
Detected Declarations
struct dpi_mps_mrrs_cfgstruct dpi_engine_cfg
Annotated Snippet
struct dpi_mps_mrrs_cfg {
__u16 max_read_req_sz; /* Max read request size */
__u16 max_payload_sz; /* Max payload size */
__u16 port; /* Ebus port */
__u16 reserved; /* Reserved */
};
struct dpi_engine_cfg {
__u64 fifo_mask; /* FIFO size mask in KBytes */
__u16 molr[DPI_MAX_ENGINES]; /* Max outstanding load requests */
__u16 update_molr; /* '1' to update engine MOLR */
__u16 reserved; /* Reserved */
};
/* DPI ioctl numbers */
#define DPI_MAGIC_NUM 0xB8
/* Set MPS & MRRS parameters */
#define DPI_MPS_MRRS_CFG _IOW(DPI_MAGIC_NUM, 1, struct dpi_mps_mrrs_cfg)
/* Set Engine FIFO configuration */
#define DPI_ENGINE_CFG _IOW(DPI_MAGIC_NUM, 2, struct dpi_engine_cfg)
#endif /* __MRVL_CN10K_DPI_H__ */
Annotation
- Immediate include surface: `linux/types.h`.
- Detected declarations: `struct dpi_mps_mrrs_cfg`, `struct dpi_engine_cfg`.
- Atlas domain: Repository Root And Misc / include.
- 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.