€•ôG      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ/translations/zh_CN/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/zh_TW/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/it_IT/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ja_JP/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/ko_KR/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ/translations/sp_SP/scsi/cxgb3i”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒcomment”“”)”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…””}”hh£sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1h¡hhhžhhŸŒ9/var/lib/git/docbuild/linux/Documentation/scsi/cxgb3i.rst”h KubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ!Chelsio S3 iSCSI Driver for Linux”h]”hŒ!Chelsio S3 iSCSI Driver for Linux”…””}”(hh»hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒIntroduction”h]”hŒIntroduction”…””}”(hhÌhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hhÉhžhhŸh³h KubhŒ	paragraph”“”)”}”(hXC  The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc.
series of products) support iSCSI acceleration and iSCSI Direct Data Placement
(DDP) where the hardware handles the expensive byte touching operations, such
as CRC computation and verification, and direct DMA to the final host memory
destination:”h]”hXC  The Chelsio T3 ASIC based Adapters (S310, S320, S302, S304, Mezz cards, etc.
series of products) support iSCSI acceleration and iSCSI Direct Data Placement
(DDP) where the hardware handles the expensive byte touching operations, such
as CRC computation and verification, and direct DMA to the final host memory
destination:”…””}”(hhÜhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K
hhÉhžhubhŒblock_quote”“”)”}”(hXƒ  - iSCSI PDU digest generation and verification

  On transmitting, Chelsio S3 h/w computes and inserts the Header and
  Data digest into the PDUs.
  On receiving, Chelsio S3 h/w computes and verifies the Header and
  Data digest of the PDUs.

- Direct Data Placement (DDP)

  S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
  payload into pre-posted final destination host-memory buffers based
  on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
  in Data-Out PDUs.

- PDU Transmit and Recovery

  On transmitting, S3 h/w accepts the complete PDU (header + data)
  from the host driver, computes and inserts the digests, decomposes
  the PDU into multiple TCP segments if necessary, and transmit all
  the TCP segments onto the wire. It handles TCP retransmission if
  needed.

  On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
  segments, separating the header and data, calculating and verifying
  the digests, then forwarding the header to the host. The payload data,
  if possible, will be directly placed into the pre-posted host DDP
  buffer. Otherwise, the payload data will be sent to the host too.
”h]”hŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒèiSCSI PDU digest generation and verification

On transmitting, Chelsio S3 h/w computes and inserts the Header and
Data digest into the PDUs.
On receiving, Chelsio S3 h/w computes and verifies the Header and
Data digest of the PDUs.
”h]”(hÛ)”}”(hŒ,iSCSI PDU digest generation and verification”h]”hŒ,iSCSI PDU digest generation and verification”…””}”(hhûhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khh÷ubhÛ)”}”(hŒ¹On transmitting, Chelsio S3 h/w computes and inserts the Header and
Data digest into the PDUs.
On receiving, Chelsio S3 h/w computes and verifies the Header and
Data digest of the PDUs.”h]”hŒ¹On transmitting, Chelsio S3 h/w computes and inserts the Header and
Data digest into the PDUs.
On receiving, Chelsio S3 h/w computes and verifies the Header and
Data digest of the PDUs.”…””}”(hj	  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khh÷ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhhòubhö)”}”(hŒõDirect Data Placement (DDP)

S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
payload into pre-posted final destination host-memory buffers based
on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
in Data-Out PDUs.
”h]”(hÛ)”}”(hŒDirect Data Placement (DDP)”h]”hŒDirect Data Placement (DDP)”…””}”(hj!  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj  ubhÛ)”}”(hŒ×S3 h/w can directly place the iSCSI Data-In or Data-Out PDU's
payload into pre-posted final destination host-memory buffers based
on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
in Data-Out PDUs.”h]”hŒÙS3 h/w can directly place the iSCSI Data-In or Data-Out PDUâ€™s
payload into pre-posted final destination host-memory buffers based
on the Initiator Task Tag (ITT) in Data-In or Target Task Tag (TTT)
in Data-Out PDUs.”…””}”(hj/  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h Khj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhhòubhö)”}”(hXz  PDU Transmit and Recovery

On transmitting, S3 h/w accepts the complete PDU (header + data)
from the host driver, computes and inserts the digests, decomposes
the PDU into multiple TCP segments if necessary, and transmit all
the TCP segments onto the wire. It handles TCP retransmission if
needed.

On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
segments, separating the header and data, calculating and verifying
the digests, then forwarding the header to the host. The payload data,
if possible, will be directly placed into the pre-posted host DDP
buffer. Otherwise, the payload data will be sent to the host too.
”h]”(hÛ)”}”(hŒPDU Transmit and Recovery”h]”hŒPDU Transmit and Recovery”…””}”(hjG  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KhjC  ubhÛ)”}”(hX  On transmitting, S3 h/w accepts the complete PDU (header + data)
from the host driver, computes and inserts the digests, decomposes
the PDU into multiple TCP segments if necessary, and transmit all
the TCP segments onto the wire. It handles TCP retransmission if
needed.”h]”hX  On transmitting, S3 h/w accepts the complete PDU (header + data)
from the host driver, computes and inserts the digests, decomposes
the PDU into multiple TCP segments if necessary, and transmit all
the TCP segments onto the wire. It handles TCP retransmission if
needed.”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K hjC  ubhÛ)”}”(hXN  On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
segments, separating the header and data, calculating and verifying
the digests, then forwarding the header to the host. The payload data,
if possible, will be directly placed into the pre-posted host DDP
buffer. Otherwise, the payload data will be sent to the host too.”h]”hXN  On receiving, S3 h/w recovers the iSCSI PDU by reassembling TCP
segments, separating the header and data, calculating and verifying
the digests, then forwarding the header to the host. The payload data,
if possible, will be directly placed into the pre-posted host DDP
buffer. Otherwise, the payload data will be sent to the host too.”…””}”(hjc  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K&hjC  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhhòubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1hðhŸh³h Khhìubah}”(h]”h ]”h"]”h$]”h&]”uh1hêhŸh³h KhhÉhžhubhÛ)”}”(hŒˆThe cxgb3i driver interfaces with open-iscsi initiator and provides the iSCSI
acceleration through Chelsio hardware wherever applicable.”h]”hŒˆThe cxgb3i driver interfaces with open-iscsi initiator and provides the iSCSI
acceleration through Chelsio hardware wherever applicable.”…””}”(hj…  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K,hhÉhžhubeh}”(h]”Œintroduction”ah ]”h"]”Œintroduction”ah$]”h&]”uh1h´hh¶hžhhŸh³h Kubhµ)”}”(hhh]”(hº)”}”(hŒUsing the cxgb3i Driver”h]”hŒUsing the cxgb3i Driver”…””}”(hjž  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¹hj›  hžhhŸh³h K0ubhÛ)”}”(hŒMThe following steps need to be taken to accelerates the open-iscsi initiator:”h]”hŒMThe following steps need to be taken to accelerates the open-iscsi initiator:”…””}”(hj¬  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K2hj›  hžhubhŒenumerated_list”“”)”}”(hhh]”(hö)”}”(hXu  Load the cxgb3i driver: "modprobe cxgb3i"

The cxgb3i module registers a new transport class "cxgb3i" with open-iscsi.

* in the case of recompiling the kernel, the cxgb3i selection is located at::

     Device Drivers
             SCSI device support --->
                     [*] SCSI low-level drivers  --->
                             <M>   Chelsio S3xx iSCSI support
”h]”(hÛ)”}”(hŒ)Load the cxgb3i driver: "modprobe cxgb3i"”h]”hŒ-Load the cxgb3i driver: â€œmodprobe cxgb3iâ€”…””}”(hjÃ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K4hj¿  ubhÛ)”}”(hŒKThe cxgb3i module registers a new transport class "cxgb3i" with open-iscsi.”h]”hŒOThe cxgb3i module registers a new transport class â€œcxgb3iâ€ with open-iscsi.”…””}”(hjÑ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K6hj¿  ubhñ)”}”(hhh]”hö)”}”(hŒóin the case of recompiling the kernel, the cxgb3i selection is located at::

   Device Drivers
           SCSI device support --->
                   [*] SCSI low-level drivers  --->
                           <M>   Chelsio S3xx iSCSI support
”h]”(hÛ)”}”(hŒKin the case of recompiling the kernel, the cxgb3i selection is located at::”h]”hŒJin the case of recompiling the kernel, the cxgb3i selection is located at:”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K8hjâ  ubhŒliteral_block”“”)”}”(hŒ™Device Drivers
        SCSI device support --->
                [*] SCSI low-level drivers  --->
                        <M>   Chelsio S3xx iSCSI support”h]”hŒ™Device Drivers
        SCSI device support --->
                [*] SCSI low-level drivers  --->
                        <M>   Chelsio S3xx iSCSI support”…””}”hjö  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jô  hŸh³h K:hjâ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhjß  ubah}”(h]”h ]”h"]”h$]”h&]”j}  Œ*”uh1hðhŸh³h K8hj¿  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhj¼  hžhhŸNh Nubhö)”}”(hXÒ  Create an interface file located under /etc/iscsi/ifaces/ for the new
transport class "cxgb3i".

The content of the file should be in the following format::

     iface.transport_name = cxgb3i
     iface.net_ifacename = <ethX>
     iface.ipaddress = <iscsi ip address>

* if iface.ipaddress is specified, <iscsi ip address> needs to be either the
  same as the ethX's ip address or an address on the same subnet. Make
  sure the ip address is unique in the network.
”h]”(hÛ)”}”(hŒ_Create an interface file located under /etc/iscsi/ifaces/ for the new
transport class "cxgb3i".”h]”hŒcCreate an interface file located under /etc/iscsi/ifaces/ for the new
transport class â€œcxgb3iâ€.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h K?hj  ubhÛ)”}”(hŒ;The content of the file should be in the following format::”h]”hŒ:The content of the file should be in the following format:”…””}”(hj)  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KBhj  ubjõ  )”}”(hŒ_iface.transport_name = cxgb3i
iface.net_ifacename = <ethX>
iface.ipaddress = <iscsi ip address>”h]”hŒ_iface.transport_name = cxgb3i
iface.net_ifacename = <ethX>
iface.ipaddress = <iscsi ip address>”…””}”hj7  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jô  hŸh³h KDhj  ubhñ)”}”(hhh]”hö)”}”(hŒ¾if iface.ipaddress is specified, <iscsi ip address> needs to be either the
same as the ethX's ip address or an address on the same subnet. Make
sure the ip address is unique in the network.
”h]”hÛ)”}”(hŒ½if iface.ipaddress is specified, <iscsi ip address> needs to be either the
same as the ethX's ip address or an address on the same subnet. Make
sure the ip address is unique in the network.”h]”hŒ¿if iface.ipaddress is specified, <iscsi ip address> needs to be either the
same as the ethXâ€™s ip address or an address on the same subnet. Make
sure the ip address is unique in the network.”…””}”(hjL  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KHhjH  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhjE  ubah}”(h]”h ]”h"]”h$]”h&]”j}  j  uh1hðhŸh³h KHhj  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhj¼  hžhhŸNh Nubhö)”}”(hXµ  edit /etc/iscsi/iscsid.conf
The default setting for MaxRecvDataSegmentLength (131072) is too big;
replace with a value no bigger than 15360 (for example 8192)::

     node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192

* The login would fail for a normal session if MaxRecvDataSegmentLength is
  too big.  A error message in the format of
  "cxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>."
  would be logged to dmesg.
”h]”(hÛ)”}”(hŒ edit /etc/iscsi/iscsid.conf
The default setting for MaxRecvDataSegmentLength (131072) is too big;
replace with a value no bigger than 15360 (for example 8192)::”h]”hŒŸedit /etc/iscsi/iscsid.conf
The default setting for MaxRecvDataSegmentLength (131072) is too big;
replace with a value no bigger than 15360 (for example 8192):”…””}”(hjp  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KLhjl  ubjõ  )”}”(hŒ2node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192”h]”hŒ2node.conn[0].iscsi.MaxRecvDataSegmentLength = 8192”…””}”hj~  sbah}”(h]”h ]”h"]”h$]”h&]”h±h²uh1jô  hŸh³h KPhjl  ubhñ)”}”(hhh]”hö)”}”(hŒÒThe login would fail for a normal session if MaxRecvDataSegmentLength is
too big.  A error message in the format of
"cxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>."
would be logged to dmesg.
”h]”hÛ)”}”(hŒÑThe login would fail for a normal session if MaxRecvDataSegmentLength is
too big.  A error message in the format of
"cxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>."
would be logged to dmesg.”h]”hŒÕThe login would fail for a normal session if MaxRecvDataSegmentLength is
too big.  A error message in the format of
â€œcxgb3i: ERR! MaxRecvSegmentLength <X> too big. Need to be <= <Y>.â€
would be logged to dmesg.”…””}”(hj“  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KRhj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhjŒ  ubah}”(h]”h ]”h"]”h$]”h&]”j}  j  uh1hðhŸh³h KRhjl  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1hõhj¼  hžhhŸNh Nubhö)”}”(hŒáTo direct open-iscsi traffic to go through cxgb3i's accelerated path,
"-I <iface file name>" option needs to be specified with most of the
iscsiadm command. <iface file name> is the transport interface file created
in step 2.”h]”hÛ)”}”(hŒáTo direct open-iscsi traffic to go through cxgb3i's accelerated path,
"-I <iface file name>" option needs to be specified with most of the
iscsiadm command. <iface file name> is the transport interface file created
in step 2.”h]”hŒçTo direct open-iscsi traffic to go through cxgb3iâ€™s accelerated path,
â€œ-I <iface file name>â€ option needs to be specified with most of the
iscsiadm command. <iface file name> is the transport interface file created
in step 2.”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÚhŸh³h KWhj³  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hõhj¼  hžhhŸh³h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œarabic”Œprefix”hŒsuffix”Œ.”uh1jº  hj›  hžhhŸh³h K4ubeh}”(h]”Œusing-the-cxgb3i-driver”ah ]”h"]”Œusing the cxgb3i driver”ah$]”h&]”uh1h´hh¶hžhhŸh³h K0ubeh}”(h]”Œ!chelsio-s3-iscsi-driver-for-linux”ah ]”h"]”Œ!chelsio s3 iscsi driver for linux”ah$]”h&]”uh1h´hhhžhhŸh³h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h³uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¹NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j	  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h³Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(jã  jà  j˜  j•  jÛ  jØ  uŒ	nametypes”}”(jã  ‰j˜  ‰jÛ  ‰uh}”(jà  h¶j•  hÉjØ  j›  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.