Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759385AbYBETMh (ORCPT ); Tue, 5 Feb 2008 14:12:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752427AbYBETM1 (ORCPT ); Tue, 5 Feb 2008 14:12:27 -0500 Received: from srv5.dvmed.net ([207.36.208.214]:45668 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751234AbYBETM0 (ORCPT ); Tue, 5 Feb 2008 14:12:26 -0500 Message-ID: <47A8B510.8000807@garzik.org> Date: Tue, 05 Feb 2008 14:12:16 -0500 From: Jeff Garzik User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Vladislav Bolkhovitin CC: Alan Cox , Mike Christie , linux-scsi@vger.kernel.org, Linux Kernel Mailing List , "Nicholas A. Bellinger" , James Bottomley , scst-devel@lists.sourceforge.net, Andrew Morton , Linus Torvalds , FUJITA Tomonori Subject: Re: Integration of SCST in the mainstream Linux kernel References: <1201639331.3069.58.camel@localhost.localdomain> <47A05CBD.5050803@vlnb.net> <47A7049A.9000105@vlnb.net> <1202139015.3096.5.camel@localhost.localdomain> <47A73C86.3060604@vlnb.net> <1202144767.3096.38.camel@localhost.localdomain> <47A7488B.4080000@vlnb.net> <1202145901.3096.49.camel@localhost.localdomain> <1202151989.11265.576.camel@haakon2.linux-iscsi.org> <20080204224314.113afe7b@core> <47A79A10.4070706@garzik.org> <47A8B29B.8050406@vlnb.net> In-Reply-To: <47A8B29B.8050406@vlnb.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.3 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 847 Lines: 24 Vladislav Bolkhovitin wrote: > Jeff Garzik wrote: >> iSCSI is way, way too complicated. > > I fully agree. From one side, all that complexity is unavoidable for > case of multiple connections per session, but for the regular case of > one connection per session it must be a lot simpler. Actually, think about those multiple connections... we already had to implement fast-failover (and load bal) SCSI multi-pathing at a higher level. IMO that portion of the protocol is redundant: You need the same capability elsewhere in the OS _anyway_, if you are to support multi-pathing. Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/