Re: [Iscsitarget-devel] IET Performance
Scott, Thanks to Ross for his info. Scott I am a newbie to iSCSI Enterprise Target! I have prior experience on FCoE protocol. I am working on 1G and 10G with IET as front-end. Moreover my requirement is all about to have multiple target ports(4 phy ports) with multiple session and thereby to ensure its performance. The above is applicable to 1G and 10G. I am not sure about the current implementation with zero copy. Thanks Gopala krishnan Varatharajan. On Sun, Nov 8, 2009 at 9:24 PM, Scott Kaelin wrote: > > > On Sun, Nov 8, 2009 at 4:47 AM, Gopu Krishnan wrote: > >> Hi all, >> >> I am working on iSCSI Enterprise Target. Could you please someone explain >> about the performance of the IET. >> If so how the performance was calculated and what was the througput for >> the same. >> >> Thanks >> Gopala krishnan Varatharajan >> >> >> -- >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> ___ >> Iscsitarget-devel mailing list >> iscsitarget-de...@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/iscsitarget-devel >> >> You might want to provide a little more details on exactly what you are > looking for. I know this has been discussed a number of times in the past by > Ross. He even gives his benchmarks and the hardware that he is using. > > -Scott > > > -- > Scott Kaelin > 0x6BE43783 > --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Infortrend + "iSCSI: detected conn error (1011)" + "TCP Dup ACK"
Hi all,
I am working on iSCSI En. Tar. Could you please someone explain about the
performance of the IET.
If so how the performance was calculated and what was the througput for the
same.
Thanks
Gopala krishnan Varatharajan
On Sat, Nov 7, 2009 at 3:09 AM, Matthew Dickinson <
matt-openis...@alpha345.com> wrote:
>
> On 11/6/09 3:08 PM, "Mike Christie" wrote:
>
> >
> > Could you send more of the log? Do you see a message like
> > connection1:0 is
> > operational after recovery (1 attempts)
> > after you see the conn errors (how many attempts)?
>
> Here's one particular connection:
>
> Nov 4 05:12:14 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4321648393, last ping 4321653393, now
> 4321658393
> Nov 4 05:12:14 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 05:12:21 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 05:12:46 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4321680691, last ping 4321685691, now
> 4321690691
> Nov 4 05:12:46 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 05:12:58 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:46:03 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330877890, last ping 4330882890, now
> 4330887890
> Nov 4 07:46:03 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:46:10 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:46:27 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330901733, last ping 4330906733, now
> 4330911733
> Nov 4 07:46:27 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:46:32 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:47:21 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4330955414, last ping 4330960414, now
> 4330965414
> Nov 4 07:47:21 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:47:28 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
> Nov 4 07:48:28 backup kernel: connection22:0: ping timeout of 5 secs
> expired, recv timeout 5, last rx 4331023213, last ping 4331028213, now
> 4331033213
> Nov 4 07:48:28 backup kernel: connection22:0: detected conn error (1011)
> Nov 4 07:48:35 backup iscsid: connection22:0 is operational after recovery
> (1 attempts)
>
> FWIW:
>
> [r...@backup ~]# cat /var/log/messages | grep "after recovery" | awk
> '{print
> $11" "$12}' | sort | uniq
> (113 attempts)
> (1 attempts)
> (24 attempts)
> (2 attempts)
> (3 attempts)
> (4 attempts)
> (5 attempts)
> (66 attempts)
> (68 attempts)
> (6 attempts)
> (7 attempts)
> (8 attempts)
> (9 attempts)
>
> >
> > Try disabling nops by setting
> >
> > node.conn[0].timeo.noop_out_interval = 0
> > node.conn[0].timeo.noop_out_timeout = 0
>
> Ok, I'll let you know how it pans out.
>
> Thanks,
>
> Matthew
>
>
>
> >
>
--
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to
open-iscsi+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~--~~~~--~~--~--~---
Re: Poor read performance with IET
Pryker, Test your environment with NULL I/O. Perform the read and write and check the performance which should attains around 100MB/s. If not so the problem would be around IET on your environment, Else the problem may be attained with your disk I/O or back-end driver. Thanks Gopala krishnan Varatharajan. On Tue, Nov 17, 2009 at 8:51 PM, pryker wrote: > I am currently running IET on a CentOS 5.4 server with the following > kernel: > > Linux titan1 2.6.18-128.7.1.el5 #1 SMP Mon Aug 24 08:21:56 EDT 2009 > x86_64 x86_64 x86_64 GNU/Linux > > The server is a Dual quad core 2.8 GHz system with 16 GB ram. I am > also using Coraid disk shelves via AoE for my block storage that I am > offering up as a iscsi target. > > I am running v 0.4.17 of IET. > > I am getting very good write performance but lousy read performance. > performing a simple sequential write to the iscsi target I get 94 > megabytes per sec. With reads I am only getting 12.4 megabytes per > sec. > > My ietd.conf looks like this: > > Target iqn.2009-11.net.storage:titan.diskshelf1.e1.2 > Lun 1 Path=/dev/etherd/e1.2,Type=blockio > Alias e1.2 > MaxConnections 1 > InitialR2T No > ImmediateData Yes > MaxRecvDataSegmentLength 262144 > MaxXmitDataSegmentLength 262144 > > I have also made the following tweaks to tcp/ip: > > sysctl net.ipv4.tcp_rmem="100 100 100" > sysctl net.ipv4.tcp_wmem="100 100 100" > sysctl net.ipv4.tcp_tw_recycle=1 > sysctl net.ipv4.tcp_tw_reuse=1 > sysctl net.core.rmem_max=524287 > sysctl net.core.wmem_max=524287 > sysctl net.core.wmem_default=524287 > sysctl net.core.optmem_max=524287 > sysctl net.core.netdev_max_backlog=30 > > I am using Broadcom cards in the iscsi target server. I have enabled > jumbo rames on them (MTU 9000). They are connected directly into a > windows server and I am accessing the iscsi target with MS iscsi > initiator. The NIC cards on the Windows server are also set to a MTU > of 9000. There is no switch in between, they are directly connected > into the Windows server. > > I also notice that load averages on the Linux box will get into the > 7's and 8's when I try pushing the system by performing multiple > transfers. > > Any feedback on what I might be missing here would be great! > > Thanks > > Phil > > -- > > You received this message because you are subscribed to the Google Groups > "open-iscsi" group. > To post to this group, send email to open-is...@googlegroups.com. > To unsubscribe from this group, send email to > open-iscsi+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/open-iscsi?hl=. > > > -- Regards Gopu. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
Getting the initiator/target IP address from the IET code
Hi All, Let us take there are multiple initiator and target, Assume the session/connection got established and the IO is going fine. I need to retrieve the initiator and target IP address on which a session got established, where can I hook this from the IET code. Is it possible to retrieve the IP address from struct sock. We have initiator name , target name, tid, sid, cid .. but not the IP address information. Thanks in advance Gopal -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Re: Getting the initiator/target IP address from the IET code
Thanks Ulrich, Could you please give me a detailed info on how to retrieve the initiator IP, target IP, initiator TCP port and target TCP port from the struct sock. I would like to know about the kernel api for this. I am not sure if we can use inet_sk(), to get the saddr and daddr. If so please give me more info on this. Regards Gopal. On Wed, Feb 24, 2010 at 12:37 PM, Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > On 23 Feb 2010 at 16:55, Gopu Krishnan wrote: > > > Is it possible to retrieve the IP address from struct sock. > > > > AFAIK, a socket address is a network address plus a port (maybe even > two of each in the TCP case). So the answer should be: YES > > -- > You received this message because you are subscribed to the Google Groups > "open-iscsi" group. > To post to this group, send email to open-is...@googlegroups.com. > To unsubscribe from this group, send email to > open-iscsi+unsubscr...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/open-iscsi?hl=en. > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Chap implementaion
Hi All, I am trying to connect Microsoft initiator and Linux target. Am trying to understand how the bidirectional chap happens. What is the CHAP_N will be send between the Microsoft initiator and target and vice-versa. Is there is any functionality differnce between the both? I also would like to know where we specify target secret and initiator secret in Microsoft initiator. Moreover am clear with Linux initiator and Linux target communication with respect to chap. Thanks Gopala krishnan Vartharajan -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
iSNS implementation
Hi All, Am newbie to the iSNS part of the IET implementation. Am bit confused about the implementation part in isns.c file. We create socket and have one fd in listen mode and during the event loop, based on the poll we do create socket and connect. I am not clear why and when this connect and accept descriptors are used and am not clear how this will get operate with iSNS server. My understanding is that our IET is going to be iSNS client and iSNS server is the IP address we are giving in the IETD.conf file. It would be great if someone also can explain about the frame flow (state machine) between the iSNS server and iSNS client (IET). Thanks Gopal -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
iSNS implementation
> > Hi All, > > Am newbie to the iSNS part of the IET implementation. Am bit confused about >the implementation part in isns.c file. > >We create socket and have one fd in listen mode and during the event > loop, >based on the poll we do create socket and connect. > >I am not clear why and when this connect and accept descriptors are used > and >am not clear how this will get operate with iSNS server. > >My understanding is that our IET is going to be iSNS client and iSNS > server >is the IP address we are giving in the IETD.conf file. > >It would be great if someone also can explain about the frame flow > (state >machine) between the iSNS server and iSNS client (IET). > > Thanks > Gopal > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
iSNS implementation
Hi All, Can someone explain about what is the usage of this "print_scn_pdu()" function defined in isns.c file. Thanks Gopal. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
target creation and isns scn notification
Hi All, In IET code, we create the target before the isns init. I understand that for per target we do have the isns scn registration. But we do SCN registration only for the targets which are created by ietadm. From that point is what the use_isns got enabled. I would like to conclude, that the SCN registration wont happen for targets which are created via ietd.conf. SCN registration will happen only for target which are created by ietadm. Moreover the device registration also wont happen for the targets created by ietd.conf. Only Device Query happens on time-out. Please confirm my observations. Thanks Gopal. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Fwd: target creation and isns scn notification
Hi All, Can someone look into this issue as mentioned in the below mail thread. I feel this is an BUG. If not please clarify on the same. Thanks Gopal. -- Forwarded message -- From: Gopu Krishnan Date: Wed, Mar 17, 2010 at 3:54 PM Subject: target creation and isns scn notification To: open-iscsi@googlegroups.com Hi All, In IET code, we create the target before the isns init. I understand that for per target we do have the isns scn registration. But we do SCN registration only for the targets which are created by ietadm. From that point is what the use_isns got enabled. I would like to conclude, that the SCN registration wont happen for targets which are created via ietd.conf. SCN registration will happen only for target which are created by ietadm. Moreover the device registration also wont happen for the targets created by ietd.conf. Only Device Query happens on time-out. Please confirm my observations. Thanks Gopal. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
Broadcom driver update
Hi, Currently am using 1G Netextreme Gigabit ethernet card. Any one knows how to update the flash. Is there is any possible to update the iSCSI TOE into the 1G BCM board. Thanks Gopala krishnan varatharajan. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.
