drivers/infiniband/ulp/isert/ib_isert.c

File Facts

System

Linux kernel

Corpus path

drivers/infiniband/ulp/isert/ib_isert.c

Extension

.c

Size

72656 bytes

Lines

2669

Domain

Driver Families

Bucket

drivers/infiniband

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/string.h
• linux/module.h
• linux/scatterlist.h
• linux/socket.h
• linux/in.h
• linux/in6.h
• rdma/ib_verbs.h
• rdma/ib_cm.h
• rdma/rdma_cm.h
• target/target_core_base.h
• target/target_core_fabric.h
• target/iscsi/iscsi_transport.h
• linux/semaphore.h
• ib_isert.h

Detected Declarations

• function isert_sg_tablesize_set
• function isert_prot_cmd
• function isert_qp_event_callback
• function isert_create_qp
• function isert_alloc_rx_descriptors
• function isert_free_rx_descriptors
• function isert_create_device_ib_res
• function isert_free_device_ib_res
• function isert_device_put
• function isert_device_get
• function isert_init_conn
• function isert_free_login_buf
• function isert_alloc_login_buf
• function isert_set_nego_params
• function isert_destroy_qp
• function isert_connect_request
• function isert_connect_release
• function isert_connected_handler
• function isert_release_kref
• function isert_put_conn
• function isert_handle_unbound_conn
• function isert_conn_terminate
• function isert_np_cma_handler
• function isert_disconnected_handler
• function isert_connect_error
• function isert_cma_handler
• function isert_post_recvm
• function isert_post_recv
• function isert_login_post_send
• function __isert_create_send_desc
• function isert_create_send_desc
• function isert_init_tx_hdrs
• function isert_init_send_wr
• function isert_login_post_recv
• function isert_put_login_tx
• function isert_rx_login_req
• function isert_handle_scsi_cmd
• function isert_handle_iscsi_dataout
• function isert_handle_nop_out
• function isert_handle_text_cmd
• function isert_rx_opcode
• function isert_print_wc
• function isert_recv_done
• function isert_login_recv_done
• function isert_rdma_rw_ctx_destroy
• function isert_put_cmd
• function target_put_sess_cmd
• function isert_unmap_tx_desc

Annotated Snippet

module_init(isert_init);
module_exit(isert_exit);

Annotation

• Immediate include surface: `linux/string.h`, `linux/module.h`, `linux/scatterlist.h`, `linux/socket.h`, `linux/in.h`, `linux/in6.h`, `rdma/ib_verbs.h`, `rdma/ib_cm.h`.
• Detected declarations: `function isert_sg_tablesize_set`, `function isert_prot_cmd`, `function isert_qp_event_callback`, `function isert_create_qp`, `function isert_alloc_rx_descriptors`, `function isert_free_rx_descriptors`, `function isert_create_device_ib_res`, `function isert_free_device_ib_res`, `function isert_device_put`, `function isert_device_get`.
• Atlas domain: Driver Families / drivers/infiniband.
• 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.