drivers/net/ethernet/intel/ice/virt/queues.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/intel/ice/virt/queues.h

Extension

.h

Size

634 bytes

Lines

21

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.h

Detected Declarations

• struct ice_vf

Annotated Snippet

#ifndef _ICE_VIRT_QUEUES_H_
#define _ICE_VIRT_QUEUES_H_

#include <linux/types.h>

struct ice_vf;

u16 ice_vc_get_max_frame_size(struct ice_vf *vf);
int ice_vc_ena_qs_msg(struct ice_vf *vf, u8 *msg);
int ice_vc_dis_qs_msg(struct ice_vf *vf, u8 *msg);
int ice_vc_cfg_irq_map_msg(struct ice_vf *vf, u8 *msg);
int ice_vc_cfg_q_bw(struct ice_vf *vf, u8 *msg);
int ice_vc_cfg_q_quanta(struct ice_vf *vf, u8 *msg);
int ice_vc_cfg_qs_msg(struct ice_vf *vf, u8 *msg);
int ice_vc_request_qs_msg(struct ice_vf *vf, u8 *msg);

#endif /* _ICE_VIRT_QUEUES_H_ */

Annotation

• Immediate include surface: `linux/types.h`.
• Detected declarations: `struct ice_vf`.
• 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.