drivers/net/ethernet/huawei/hinic/hinic_rx.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/huawei/hinic/hinic_rx.h

Extension

.h

Size

1117 bytes

Lines

52

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
• linux/netdevice.h
• linux/u64_stats_sync.h
• linux/interrupt.h
• hinic_hw_qp.h

Detected Declarations

• struct hinic_rxq_stats
• struct hinic_rxq

Annotated Snippet

struct hinic_rxq_stats {
	u64                     pkts;
	u64                     bytes;
	u64			errors;
	u64			csum_errors;
	u64			other_errors;
	u64			alloc_skb_err;
	struct u64_stats_sync   syncp;
};

struct hinic_rxq {
	struct net_device       *netdev;
	struct hinic_rq         *rq;

	struct hinic_rxq_stats  rxq_stats;

	char                    *irq_name;
	u16			buf_len;
	u32			rx_buff_shift;

	struct napi_struct      napi;
};

void hinic_rxq_get_stats(struct hinic_rxq *rxq, struct hinic_rxq_stats *stats);

int hinic_init_rxq(struct hinic_rxq *rxq, struct hinic_rq *rq,
		   struct net_device *netdev);

void hinic_clean_rxq(struct hinic_rxq *rxq);

#endif

Annotation

• Immediate include surface: `linux/types.h`, `linux/netdevice.h`, `linux/u64_stats_sync.h`, `linux/interrupt.h`, `hinic_hw_qp.h`.
• Detected declarations: `struct hinic_rxq_stats`, `struct hinic_rxq`.
• 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.