From: Alexei_Roudnev (Alexei_Roudnev_at_exigengroup.com)
Date: Wed Jan 17 2007 - 03:55:13 CET
Message-ID: <0cd301c739e2$e8fa7a30$6f31a8c0@sjc.exigengroup.com> From: "Alexei_Roudnev" <Alexei_Roudnev@exigengroup.com> Date: Tue, 16 Jan 2007 18:55:13 -0800 Subject: Re: [suse-sles-e] iSCSI on SLES10 - open-iscsi vs cisco iscsi
> it is not that easy i feel. for example, u can send your ini code to IOL
> lab to do interoperability test, you need to test so many possibilities.
> all these need many resources. back to one word, money.
>
This is true. On the other hand, most of the problems was not because of
interoperaqbility problems, but because of some kinds of race condition /
heavy load problems, and this kind of thigs are easier to reveal in tests
(many techniques do exists, such as artifically slow servers with multi cpu,
running long performance tests all the time, and so so on...).
But I am more interested in open-iscsi quality - old Cisco iSCSI initiator
was well tested and was widely used; how new open-iscsi driver have been
used in real world? Sometimes, _merge_ means that developers was able to
merge primary code from the old system into the utilities from the new
system (and then such merge is safe); in other cases, when kernel was
changed sugnificantly, there is a high risk of bugs.
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Wed Jan 17 2007 - 05:58:09 CET