drivers/scsi/cxgbi/libcxgbi.c

File Facts

System

Linux kernel

Corpus path

drivers/scsi/cxgbi/libcxgbi.c

Extension

.c

Size

79952 bytes

Lines

3098

Domain

Driver Families

Bucket

drivers/scsi

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/skbuff.h
• linux/crypto.h
• linux/scatterlist.h
• linux/pci.h
• scsi/scsi.h
• scsi/scsi_cmnd.h
• scsi/scsi_host.h
• linux/if_vlan.h
• linux/inet.h
• net/dst.h
• net/route.h
• net/ipv6.h
• net/ip6_route.h
• net/addrconf.h
• linux/inetdevice.h
• linux/module.h
• net/tcp.h
• libcxgbi.h

Detected Declarations

• function cxgbi_decode_sw_tag
• function cxgbi_device_portmap_create
• function cxgbi_device_portmap_cleanup
• function cxgbi_device_destroy
• function cxgbi_device_unregister
• function cxgbi_device_unregister_all
• function cxgbi_hbas_remove
• function cxgbi_hbas_add
• function sock_get_port
• function sock_put_port
• function cxgbi_sock_free_cpl_skbs
• function cxgbi_check_route
• function cxgbi_check_route6
• function cxgbi_sock_established
• function cxgbi_inform_iscsi_conn_closing
• function cxgbi_sock_closed
• function need_active_close
• function cxgbi_sock_fail_act_open
• function cxgbi_sock_act_open_req_arp_failure
• function cxgbi_sock_rcv_abort_rpl
• function cxgbi_sock_rcv_peer_close
• function cxgbi_sock_rcv_close_conn_rpl
• function cxgbi_sock_rcv_wr_ack
• function cxgbi_sock_find_best_mtu
• function cxgbi_sock_select_mss
• function cxgbi_sock_skb_entail
• function cxgbi_sock_purge_wr_queue
• function cxgbi_sock_check_wr_invariants
• function scmd_get_params
• function cxgbi_ddp_set_one_ppod
• function cxgbi_ddp_ppm_setup
• function cxgbi_ddp_sgl_check
• function cxgbi_ddp_reserve
• function task_release_itt
• function cxgbi_ppm_is_ddp_tag
• function cxgbi_build_sw_tag
• function task_reserve_itt
• function cxgbi_parse_pdu_itt
• function cxgbi_conn_tx_open
• function read_pdu_skb
• function skb_read_pdu_bhs
• function skb_read_pdu_data
• function csk_return_rx_credits
• function cxgbi_conn_pdu_ready
• function sgl_seek_offset
• function for_each_sg
• function sgl_read_to_frags
• function cxgbi_task_data_sgl_check

Annotated Snippet

module_init(libcxgbi_init_module);
module_exit(libcxgbi_exit_module);

Annotation

• Immediate include surface: `linux/skbuff.h`, `linux/crypto.h`, `linux/scatterlist.h`, `linux/pci.h`, `scsi/scsi.h`, `scsi/scsi_cmnd.h`, `scsi/scsi_host.h`, `linux/if_vlan.h`.
• Detected declarations: `function cxgbi_decode_sw_tag`, `function cxgbi_device_portmap_create`, `function cxgbi_device_portmap_cleanup`, `function cxgbi_device_destroy`, `function cxgbi_device_unregister`, `function cxgbi_device_unregister_all`, `function cxgbi_hbas_remove`, `function cxgbi_hbas_add`, `function sock_get_port`, `function sock_put_port`.
• Atlas domain: Driver Families / drivers/scsi.
• 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.