7–iSCSI Configuration
Software Components
103
AH0054602-00 A
iSCSI Crash Dump
Crash dump functionality is currently supported only for offload iSCSI boot for the
FastLinQ 41
xxx
Series Adapters. No additional configurations are required to
configure iSCSI crash dump generation when in offload iSCSI boot mode.
Software Components
The QLogic FastLinQ 41
xxx
iSCSI software consists of a single kernel module
called qedi.ko (qedi). The qedi module is dependent on additional parts of the
Linux kernel for specific functionality:
qed.ko
is the Linux eCore kernel module used for common QLogic
FastLinQ 41
xxx
hardware initialization routines.
scsi_transport_iscsi.ko
is the Linux iSCSI transport library used for
upcall and downcall for session management.
libiscsi.ko
is the Linux iSCSI lib function needed for protocol data unit
(PDU) and task processing, as well as session memory management.
iscsi_boot_sysfs.ko
is the Linux iSCSI sysfs interface that provides
helpers to export iSCSI boot information.
uio.ko
is the Linux Userspace I/O interface, used for light L2 memory
mapping for iscsiuio.
These modules must be loaded before qedi can be functional. Otherwise, you
might encounter an “unresolved symbol” error. If the qedi module is installed in the
distribution update path, the requisite will be automatically loaded by modprobe.
Differences from bnx2i
Some key differences exist between qedi—the driver for the QLogic FastLinQ
41
xxx
Series Adapter (iSCSI)—and the previous QLogic iSCSI offload
driver—bnx2i for the QLogic 8400 Series Adapters. Some of these differences
include:
qedi directly binds to a PCI function exposed by the CNA.
qedi does not sit on top of the net_device.
qedi is not dependent on a network driver such as bnx2x and cnic.
qedi is not dependent on cnic, but it has dependency on qed.
qedi is responsible for exporting boot information in sysfs using
iscsi_boot_sysfs.ko
, whereas bnx2i boot from SAN relies on the
iscsi_ibft.ko
module for exporting boot information.
