On Sun, Jul 24, 2011 Mike Christie wrote: > I think where doing a kernel/userspace split is going to be more > difficult is with supporting hw iscsi targets. With software iscsi you > can just pass down a socket and the settings more or less. With hw > iscsi, you want to be able to send the login related packets through the > iscsi port using the iscsi engine or hw/fw might be doing the actual > login process. But, if you are putting discovery (isns, sendtargets, > dhcp iscsi/isns options, slp, etc) in userspace then you have to solve > those issues for discovery so you can use the same interfaces for both. iSCSI HBAs first appeared considerable time ago. Since then several new and interesting technologies appeared, e.g. iWARP and RoCE. Why should one spend time on supporting target mode for iSCSI HBAs instead of investing time in supporting iWARP HBAs or RoCE HBAs ? An additional advantage is that the last two options allow to use iSER instead of iSCSI. In case someone is not familiar with one of the acronyms mentioned above: iWARP = Internet Wide Area RDMA Protocol, a technology that makes high-bandwidth low-latency communication possible over TCP/IP networks. RoCE = RDMA over Converged Ethernet, a technology that makes high-bandwidth low-latency communication possible over DCB Ethernet networks. Sometimes called InfiniBand over Ethernet (IBoE). DCB = Data Center Bridging, a set of standards that allow enhanced communication over an Ethernet network. DCB is sometimes called Converged Enhanced Ethernet (CEE). Alex. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
