Re: Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.18 ?
What distro are you running and what version? Why are you using such a old kernel? Is this a RHEL 5 based distro? If so, it is best to use the tools/kernel modules that come with it. They are pretty up to date and stable. On Aug 20, 2014, at 10:44 PM, loulang...@163.com wrote: Any help or hint to compile open-iscsi-2.0-870.2 for kernel 2.6.28 ? [root@SPA open-iscsi]# uname -a Linux SPA 2.6.18-194.17.1.b1.07 #12 SMP Wed Jun 18 15:22:13 CST 2014 x86_64 x86_64 x86_64 GNU/Linux [root@SPA open-iscsi]# gcc -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --enable-plugin --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux Thread model: posix gcc version 4.1.2 20080704 (Red Hat 4.1.2-48) [root@SPA open-iscsi]# make make -C utils/open-isns make[1]: Entering directory `/home/colibri/repos/open-iscsi/utils/open-isns' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/colibri/repos/open-iscsi/utils/open-isns' make -C utils/sysdeps make[1]: Entering directory `/home/colibri/repos/open-iscsi/utils/sysdeps' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/colibri/repos/open-iscsi/utils/sysdeps' make -C utils/fwparam_ibft make[1]: Entering directory `/home/colibri/repos/open-iscsi/utils/fwparam_ibft' cc -O2 -g -fPIC -Wall -Wstrict-prototypes -I../../include -I../../usr -D_GNU_SOURCE -c -o ../../usr/iscsi_net_util.o ../../usr/iscsi_net_util.c In file included from ../../usr/iscsi_net_util.c:32: ../../usr/ethtool-copy.h:24: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h: In function 'ethtool_cmd_speed_set': ../../usr/ethtool-copy.h:44: error: 'struct ethtool_cmd' has no member named 'speed_hi' ../../usr/ethtool-copy.h: In function 'ethtool_cmd_speed': ../../usr/ethtool-copy.h:49: error: 'struct ethtool_cmd' has no member named 'speed_hi' ../../usr/ethtool-copy.h: At top level: ../../usr/ethtool-copy.h:76: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:90: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:99: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:251: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:278: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:304: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:311: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:317: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:322: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:333: error: expected specifier-qualifier-list before '__u8' ../../usr/ethtool-copy.h:349: error: expected specifier-qualifier-list before '__u8' make[1]: *** [../../usr/iscsi_net_util.o] Error 1 make[1]: Leaving directory `/home/colibri/repos/open-iscsi/utils/fwparam_ibft' make: *** [user] Error 2 Thanks for your help? -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: iscsi over RBD performance tips?
Are you using linux for the initiator? If so, what is the throughput you get from just using this open-iscsi initiator connected to tgt with a ram disk? I just installed RBD here for work, so let me check it out. What io tool are using and if it is something like fio could you post the arguments you used to run it? On Aug 21, 2014, at 4:10 PM, Wyllys Ingersoll wyl...@gmail.com wrote: Im looking for suggestions about maximizing performance when using an RBD backend (Ceph) over a 10GB Ethernet link. In my testing, I see the read throughput max out at about 100Mbyte/second for just about any block sizes above 4K (below 4K it becomes horribly slow) and write operations are about 40Mbyte/second. Using librados directly to read from the same backend pool/image yields much higher numbers, so the issue seems to be in the iscsi/bs_rbd backend. Regardless of the data sizes being read, the max thruput I am seeing is about 80% slower than using librados directly. Any suggestions would be much appreciated. thanks, Wyllys -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Best way to create multiple TCP flows on 10 Gbps link
On Aug 22, 2014, at 12:07 PM, Redwood Hyd redwood...@gmail.com wrote: Hi All, I am trying to achieve10Gbps in my single initiator/single target env. (open-iscsi and IET) I exported 3 Ramdisks, via 3 different IP aliases to initator, did three iscsi logins , 3 mounts points and then 3 fio jobs in parallel (256K block size each). Question 1) Is above a real use case where from same iscsi initiator i did 3 iscsi logins to same target (via different IP addresses) ? Anything pros/cons with this. This seems normal. Question 2) What are the other best ways to create parallel TCP flows (because it seems open-iscsi does'nt have MC/S support) Multiple sessions to different portals then use dm-multipath over all those paths/sessions to the LU. Question 3) In this scenario can I use dm-multipath - can someone suggest most common way so that at TCP level i get multiple flows. What you described above, when you run /sbin/multipath /sbin/multipath -ll Do you see each device having 3 paths? Did you set it up to do round robin for dm multipath path selection? If so, each path is going to be a different tcp socket connection which the iscsi initiator and dm-multipath will use to send IO on. At my last job, fusion-io/sandisk, we sold a high performance target, and to get the highest throughput when using linux we had to create extra sessions/connections to avoid some bottlenecks in the linux block/scsi layer. Above you would have a session to each target portal/ip. We would set node.session.nr_sessions in iscsid.conf to greater than one so each portal would have nr_sessions sessions/connections. When you run iscsiadm -m node -T target -p ip -l, iscsiadm would then create nr_session to that portal. iscsiadm -m session would show the extra sessions when logged in and multipath -ll should show the extra paths. You can also just do iscsiadm -m session -R SID -o new to dynamically add another session/connection. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
