Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762855AbYBFARt (ORCPT ); Tue, 5 Feb 2008 19:17:49 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760723AbYBFARl (ORCPT ); Tue, 5 Feb 2008 19:17:41 -0500 Received: from smtp117.sbc.mail.sp1.yahoo.com ([69.147.64.90]:24233 "HELO smtp117.sbc.mail.sp1.yahoo.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1760091AbYBFARj (ORCPT ); Tue, 5 Feb 2008 19:17:39 -0500 X-YMail-OSG: aBRSIZIVM1mjGTSM8aqBL5fMajpUqSRjF4jBfT2Itaa2rQgelSodzebD9muGPwzOPXcAgMYSI2m9Kyy1aa1_PcFaEE6NuCnMvx2fSIxWUenHlwKpTw-- X-Yahoo-Newman-Property: ymail-3 Subject: Re: Integration of SCST in the mainstream Linux kernel From: "Nicholas A. Bellinger" To: Jeff Garzik Cc: Vladislav Bolkhovitin , Alan Cox , Mike Christie , linux-scsi@vger.kernel.org, Linux Kernel Mailing List , James Bottomley , scst-devel@lists.sourceforge.net, Andrew Morton , Linus Torvalds , FUJITA Tomonori , Julian Satran In-Reply-To: <47A8B510.8000807@garzik.org> 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> Content-Type: text/plain Date: Tue, 05 Feb 2008 16:17:10 -0800 Message-Id: <1202257030.2220.90.camel@haakon2.linux-iscsi.org> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1500 Lines: 47 On Tue, 2008-02-05 at 14:12 -0500, Jeff Garzik wrote: > 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 > > Hey Jeff, I put a whitepaper on the LIO cluster recently about this topic.. It is from a few years ago but the datapoints are very relevant. http://linux-iscsi.org/builds/user/nab/Inter.vs.OuterNexus.Multiplexing.pdf The key advantage to MC/S and ERL=2 has always been that they are completely OS independent. They are designed to work together and actually benefit from one another. They are also are protocol independent between Traditional iSCSI and iSER. --nab PS: A great thanks for my former colleague Edward Cheng for putting this together. > > -- 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/