
Chapter X. iSCSI PDU Offload Target
Chelsio Unified Wire for Linux
151
T420-CR
T440-CR
T422-CR
T404-BT
T420-BCH
T440-LP-CR
T420-BT
T420-LL-CR
T420-CX
Adapter Requirements
The Chelsio iSCSI PDU Offload Target software can be used with or without hardware protocol
offload technology. There are two modes of operation using the iSCSI PDU Offload Target
software on Ethernet-based adapters:
Regular NIC
– The software can be used in non-offloaded (regular NIC) mode. Please note
however that this is the least optimal mode of operating the software in terms of performance.
iSCSI HW Acceleration
– In addition to offloading the TCP/IP protocols in hardware (TOE),
this mode also takes advantage of Chelsio’s ASIC capability of hardware assisted iSCSI data
and header digest calculations as well as using the direct data placement (DDP) feature.
Storage Requirements
When using the Chelsio iSCSI target, a minimum of one hardware storage device is required.
This device can be any of the device types that are supported (block, virtual block, RAM disk).
Multiple storage devices are allowed by configuring the devices to one target or the devices to
multiple targets. The software allows multiple targets to share the same device but use caution
when doing this.
Chelsio’s implementation of the target iSCSI stack has flexibility to accommodate a large range
of configurations. For quick testing, using a RAM Disk as the block storage device works nicely.
For deployment in a production environment a more sophisticated system would be needed. That
typically consists of a system with one or more storage controllers with multiple disk drives
attached running software or hardware based RAID.
1.3.
Software Requirements
chiscsi_base.ko
is iSCSI non-offload target mode driver and
chiscsi_t4.ko
is iSCSI PDU
offload target mode driver.
cxgb4, toecore, t4_tom and chiscsi_base
modules
are required by
chiscsi_t4.ko
module to
work in offloaded mode. Whereas in iscsi non-offloaded target (NIC) mode, only
cxgb4
is needed
by
chiscsi_base.ko
module.
Summary of Contents for Terminator 6
Page 1: ...Chelsio Unified Wire for Linux i...
Page 15: ...Chapter I Chelsio Unified Wire Chelsio Unified Wire for Linux 15 I Chelsio Unified Wire...
Page 51: ...Chapter II Network NIC TOE Chelsio Unified Wire for Linux 51 II Network NIC TOE...
Page 82: ...Chapter IV iWARP RDMA Chelsio Unified Wire for Linux 82 IV iWARP RDMA...
Page 99: ...Chapter V iSER Chelsio Unified Wire for Linux 99 V iSER...
Page 107: ...Chapter VI WD UDP Chelsio Unified Wire for Linux 107 VI WD UDP...
Page 119: ...Chapter VII WD TOE Chelsio Unified Wire for Linux 119 VII WD TOE...
Page 125: ...Chapter VIII NVMe oF Chelsio Unified Wire for Linux 125 VIII NVMe oF...
Page 198: ...Chapter XII Crypto Offload Chelsio Unified Wire for Linux 198 XII Crypto Offload...
Page 230: ...Chapter XIV FCoE Full Offload Initiator Chelsio Unified Wire for Linux 230...
Page 235: ...Chapter XV Offload Bonding Chelsio Unified Wire for Linux 235 XV Offload Bonding...
Page 258: ...Chapter XVIII Offload IPv6 Chelsio Unified Wire for Linux 258 XVIII Offload IPv6...
Page 311: ...Chapter XXII Ring Backbone Chelsio Unified Wire for Linux 311 XXII Ring Backbone...
Page 317: ...Chapter XXIII Traffic Management Chelsio Unified Wire for Linux 317 XXIII Traffic Management...
Page 329: ...Chapter XXIV DPDK Driver Chelsio Unified Wire for Linux 329 XXIV DPDK Driver...
Page 347: ...Chapter XXV Unified Boot Chelsio Unified Wire for Linux 347 XXV Unified Boot...
Page 357: ...Chapter XXV Unified Boot Chelsio Unified Wire for Linux 357 iv Boot to EFI Shell...
Page 427: ...Chapter XXVI Appendix A Chelsio Unified Wire for Linux 427 XXVI Appendix A...