Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759971AbYBETWW (ORCPT ); Tue, 5 Feb 2008 14:22:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759247AbYBETV6 (ORCPT ); Tue, 5 Feb 2008 14:21:58 -0500 Received: from mail-relay-01.mailcluster.net ([77.221.130.213]:53497 "EHLO mail-relay-01.mailcluster.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758694AbYBETV4 (ORCPT ); Tue, 5 Feb 2008 14:21:56 -0500 Message-ID: <47A8B757.10101@vlnb.net> Date: Tue, 05 Feb 2008 22:21:59 +0300 From: Vladislav Bolkhovitin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.13) Gecko/20060501 Fedora/1.7.13-1.1.fc5 X-Accept-Language: en-us, ru, en MIME-Version: 1.0 To: Jeff Garzik 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> <47A8B510.8000807@garzik.org> In-Reply-To: <47A8B510.8000807@garzik.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1087 Lines: 24 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. I'm thinking about MC/S as about a way to improve performance using several physical links. There's no other way, except MC/S, to keep commands processing order in that case. So, it's really valuable property of iSCSI, although with a limited application. Vlad -- 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/