Difference between revisions of "Fedora ARM Secondary Architecture/iSCSI"

From CDOT Wiki
Jump to: navigation, search
(Created page with '= iSCSI = iSCSI is SCSI (Small Computer System Interface) block device support over Internet (TCP/IP). It's basically a way of doing a storage area network (SAN) using $20/port ...')
 
(Kernel)
Line 5: Line 5:
 
= Kernel =
 
= Kernel =
  
To test iSCSI on the [[http://zenit.senecac.on.ca/wiki/index.php/Fedora_ARM_Secondary_Architecture/OpenRD-Client]] system, a new kernel was required, with iSCSI support built-in or in modular form:
+
To test iSCSI on the [[Fedora_ARM_Secondary_Architecture/OpenRD-Client|OpenRD-Client]] system, a new kernel was required, with iSCSI support built-in or in modular form:
  
 
* Kernel sources: the upstream kernel does not have OpenRD-Client support (though it does support the OpenRD-Base). Patched source obtained from git://repo.or.cz/linux-2.6/linux-2.6-openrd.git -- see discussion at http://groups.google.com/group/openrd/browse_thread/thread/6ec7b4b39700e114
 
* Kernel sources: the upstream kernel does not have OpenRD-Client support (though it does support the OpenRD-Base). Patched source obtained from git://repo.or.cz/linux-2.6/linux-2.6-openrd.git -- see discussion at http://groups.google.com/group/openrd/browse_thread/thread/6ec7b4b39700e114

Revision as of 14:11, 17 April 2010

iSCSI

iSCSI is SCSI (Small Computer System Interface) block device support over Internet (TCP/IP). It's basically a way of doing a storage area network (SAN) using $20/port gigabit ethernet instead of $3000/port FibreChannel connections.

Kernel

To test iSCSI on the OpenRD-Client system, a new kernel was required, with iSCSI support built-in or in modular form:

Results

iSCSI seems to work. We can login to an initiator (netbsd-iscsi package on HongKong x86_64), however, under heavy load (first noticed when creating a mock buildroot cache), the target receives invalid opcodes, causing the connection to fail. Experimenting with a /proc/cpu/alignment value of 3 (fixup+warn) did not clear the issue. Using the exact same target with a F12 x86_64 initiator is successful.