drivers/net/ethernet/broadcom/cnic.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/broadcom/cnic.c

Extension

.c

Size

152992 bytes

Lines

5797

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/kernel.h
• linux/errno.h
• linux/list.h
• linux/slab.h
• linux/pci.h
• linux/init.h
• linux/netdevice.h
• linux/uio_driver.h
• linux/in.h
• linux/dma-mapping.h
• linux/delay.h
• linux/ethtool.h
• linux/if_vlan.h
• linux/prefetch.h
• linux/random.h
• linux/workqueue.h
• net/ip.h
• net/tcp.h
• net/route.h
• net/ipv6.h
• net/ip6_route.h
• net/ip6_checksum.h
• scsi/iscsi_if.h
• cnic_if.h
• bnx2.h
• bnx2x/bnx2x.h
• bnx2x/bnx2x_reg.h
• bnx2x/bnx2x_fw_defs.h
• bnx2x/bnx2x_hsi.h
• ../../../scsi/bnx2i/57xx_iscsi_constants.h
• ../../../scsi/bnx2i/57xx_iscsi_hsi.h

Detected Declarations

• function cnic_uio_open
• function cnic_uio_close
• function cnic_hold
• function cnic_put
• function csk_hold
• function csk_put
• function ulp_get
• function ulp_put
• function cnic_ctx_wr
• function cnic_ctx_tbl_wr
• function cnic_ring_ctl
• function cnic_reg_wr_ind
• function cnic_reg_rd_ind
• function cnic_ulp_ctl
• function cnic_in_use
• function cnic_spq_completion
• function cnic_get_l5_cid
• function cnic_send_nlmsg
• function cnic_iscsi_nl_msg_recv
• function cnic_offld_prep
• function cnic_close_prep
• function cnic_abort_prep
• function cnic_register_driver
• function cnic_unregister_driver
• function cnic_register_device
• function cnic_unregister_device
• function cnic_init_id_tbl
• function cnic_free_id_tbl
• function cnic_alloc_id
• function cnic_alloc_new_id
• function cnic_free_id
• function cnic_free_dma
• function cnic_setup_page_tbl
• function cnic_setup_page_tbl_le
• function cnic_alloc_dma
• function cnic_free_context
• function __cnic_free_uio_rings
• function __cnic_free_uio
• function cnic_free_uio
• function cnic_free_resc
• function cnic_alloc_context
• function cnic_bnx2_next_idx
• function cnic_bnx2_hw_idx
• function cnic_bnx2x_next_idx
• function cnic_bnx2x_hw_idx
• function cnic_alloc_kcq
• function __cnic_alloc_uio_rings
• function cnic_alloc_uio_rings

Annotated Snippet

module_init(cnic_init);
module_exit(cnic_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/list.h`, `linux/slab.h`, `linux/pci.h`, `linux/init.h`, `linux/netdevice.h`.
• Detected declarations: `function cnic_uio_open`, `function cnic_uio_close`, `function cnic_hold`, `function cnic_put`, `function csk_hold`, `function csk_put`, `function ulp_get`, `function ulp_put`, `function cnic_ctx_wr`, `function cnic_ctx_tbl_wr`.
• Atlas domain: Driver Families / drivers/net.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.