include/net/rsi_91x.h
Source file repositories/reference/linux-study-clean/include/net/rsi_91x.h
File Facts
- System
- Linux kernel
- Corpus path
include/net/rsi_91x.h- Extension
.h- Size
- 1709 bytes
- Lines
- 57
- Domain
- Networking Core
- Bucket
- Sockets, Protocols, Packet Path, And Network Policy
- Inferred role
- Networking Core: implementation source
- Status
- source implementation candidate
Why This File Exists
Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/skbuff.h
Detected Declarations
struct rsi_proto_opsstruct rsi_mod_opsenum rsi_coex_queuesenum rsi_host_intf
Annotated Snippet
struct rsi_proto_ops {
int (*coex_send_pkt)(void *priv, struct sk_buff *skb, u8 hal_queue);
enum rsi_host_intf (*get_host_intf)(void *priv);
void (*set_bt_context)(void *priv, void *context);
};
struct rsi_mod_ops {
int (*attach)(void *priv, struct rsi_proto_ops *ops);
void (*detach)(void *priv);
int (*recv_pkt)(void *priv, const u8 *msg);
};
extern const struct rsi_mod_ops rsi_bt_ops;
#endif
Annotation
- Immediate include surface: `linux/skbuff.h`.
- Detected declarations: `struct rsi_proto_ops`, `struct rsi_mod_ops`, `enum rsi_coex_queues`, `enum rsi_host_intf`.
- Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
- 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.