Re: [PATCH RFC 2/2] implement transport scan callout for iscsi

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



yes and no ...

For single session, yes.

For multiple sessions, no ... lots of different initiators with aggragate of 400K into single target.

Eddy

----- Original Message ----- From: "Ming Zhang" <mingz@xxxxxxxxxxx>
To: "open-iscsi" <open-iscsi@xxxxxxxxxxxxxxxx>
Cc: "James Bottomley" <James.Bottomley@xxxxxxxxxxxx>; "Mike Christie" <michaelc@xxxxxxxxxxx>; "'SCSI Mailing List'" <linux-scsi@xxxxxxxxxxxxxxx>
Sent: Wednesday, May 25, 2005 9:00 AM
Subject: Re: [PATCH RFC 2/2] implement transport scan callout for iscsi


about this 400K IOPS, both ini and target are using your HW solution?

ming

On Tue, 2005-05-24 at 21:28 -0400, open_iscsi wrote:
Regarding the numbers, we get 400,000 IOPS with our hardware solution
using
multiple connections and multiple micro-engines. I have not tried
multi-pathing but I can tell you that I had to count clocks to get
that
number and found that even a few extra clocks could mean a lot. So
since
multi-pathing takes a lot of extra clocks, then I think there is a
benefit.
However with a software solution the extra clocks for the multi-
pathing may
not be significant.

- : 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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux