On Wed, 2005-05-25 at 11:32 -0700, Dmitry Yusupov wrote: > Those are very strong arguments against having MC/S implemented for the > software iSCSI initiator. Especially true is (a). Not that many targets > offers MC/S, since according to RFC it implies ERL=2. > > Now, back to open-iscsi initiator business and its mainline acceptance. > We are going to met your requirement and will remove multi-connection > support before next patch-set submission. As Mike C. mentioned before, > it is fairly easy to do since the whole connection management resides in > user-space. Though it will exists as a kernel patches on our web site > (http://www.open-iscsi.org) for those who wonders. > > Are there are some other requirements we need to met besides MC/S > removal ? Actually, I don't think so. I'd like some convergence on what should be in the transport class, since there have been a set of conflicting patches from Mike Christie and Nicholas Bellinger, but that's not a requirement ... what's there already can go in and we can sort out the residue in-tree. James - : 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
