[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47A8B757.10101@vlnb.net>
Date: Tue, 05 Feb 2008 22:21:59 +0300
From: Vladislav Bolkhovitin <vst@...b.net>
To: Jeff Garzik <jeff@...zik.org>
CC: Alan Cox <alan@...rguk.ukuu.org.uk>,
Mike Christie <michaelc@...wisc.edu>,
linux-scsi@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Nicholas A. Bellinger" <nab@...ux-iscsi.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
scst-devel@...ts.sourceforge.net,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Subject: Re: Integration of SCST in the mainstream Linux kernel
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists