drivers/net/ethernet/fungible/funeth/funeth_ktls.h
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/fungible/funeth/funeth_ktls.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/fungible/funeth/funeth_ktls.h- Extension
.h- Size
- 503 bytes
- Lines
- 31
- 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
net/tls.h
Detected Declarations
struct funeth_privstruct fun_ktls_tx_ctxfunction fun_ktls_init
Annotated Snippet
struct fun_ktls_tx_ctx {
__be64 tlsid;
u32 next_seq;
};
#if IS_ENABLED(CONFIG_TLS_DEVICE)
int fun_ktls_init(struct net_device *netdev);
void fun_ktls_cleanup(struct funeth_priv *fp);
#else
static inline void fun_ktls_init(struct net_device *netdev)
{
}
static inline void fun_ktls_cleanup(struct funeth_priv *fp)
{
}
#endif
#endif /* _FUN_KTLS_H */
Annotation
- Immediate include surface: `net/tls.h`.
- Detected declarations: `struct funeth_priv`, `struct fun_ktls_tx_ctx`, `function fun_ktls_init`.
- 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.