public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: open_iscsi <ESQuicksall_open_iscsi@Comcast.net>,
	open-iscsi@googlegroups.com, Mike Christie <michaelc@cs.wisc.edu>,
	'SCSI Mailing List' <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] implement transport scan callout for iscsi
Date: Wed, 25 May 2005 11:18:05 -0400	[thread overview]
Message-ID: <4294972D.4030807@adaptec.com> (raw)
In-Reply-To: <1116982816.7710.58.camel@mulgrave>

On 05/24/05 21:00, James Bottomley wrote:
> On Tue, 2005-05-24 at 20:25 -0400, open_iscsi wrote:
> 
>>The MC/S feature of iSCSI is not multi-pathing. Multi-pathing would be the 
>>use of multiple sessions to reach the same target. Generally the two 
>>sessions would use the same InitiatorName+ISID but use different Target 
>>Portal Groups at the target. In SCSI terms, it is the same initiator 
>>accessing different SCSI ports.
> 
> 
> Well, yes, every driver vendor with a multi-path solution in-driver that
> made a single presentation to the mid-layer has argued that one...

MC/S in iSCSI can be seen as a "wide port" in SAS.

That is, commands are ordered, nexus is the same, going to the same port,
etc, etc, etc.  MC/S, has nothing to do with multipathing, which sits above
the nexus level.  With MC/S the nexus is the same.

MC/S is a good thing.

	Luben

P.S. As Eddy mentioned multipathing sits at a higher level, namely
at the session level, where you open a different session to a different
port (à la SCSI parlé).
 
> The bottom line is that implementation must be in-driver.  So every
> driver doing it this way has to have their own separate multi-path
> implementation.  Whether you call it FC/AL or MC/S (or any of the other
> buzz acronyms) it's still a driver implementation of pathing.
> 
> 
>>MC/S can be used to improve band width of a session without using 
>>multi-pathing and it belongs in the driver because it is hidden from the 
>>upper layers. Think of it like parallel wires, each carrying separate (but 
>>sequenced) commands in parallel.
> 
> 
> So far, no-one has been able to produce any figures to show that MC/S is
> significantly better than symmetric active dm-multipath to an iSCSI
> target, but if you have them, please publish them.
> 
> Hiding something from the upper layers which the upper layers could do
> equally well themselves is what's considered wrong: it adds code bloat
> with no tangible benefit.
> 
> James
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2005-05-25 15:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42936441.0b798bab.39a4.ffff9774SMTPIN_ADDED@mx.googlegroups.com>
2005-05-24 21:01 ` [PATCH RFC 2/2] implement transport scan callout for iscsi Mike Christie
2005-05-24 23:17   ` James Bottomley
2005-05-25  0:25     ` open_iscsi
2005-05-25  1:00       ` James Bottomley
2005-05-25  1:28         ` open_iscsi
2005-05-25  5:22           ` Dmitry Yusupov
2005-05-25 12:55             ` open_iscsi
2005-05-25 13:00           ` Ming Zhang
2005-05-25 13:08             ` open_iscsi
2005-05-25 15:18         ` Luben Tuikov [this message]
2005-05-25 18:04           ` James Bottomley
2005-05-25 18:32             ` Dmitry Yusupov
2005-05-25 19:42               ` James Bottomley
2005-05-26  1:38             ` open_iscsi
2005-05-25  2:20 open_iscsi
  -- strict thread matches above, loose matches on Subject: below --
2005-05-21 21:39 Mike Christie
2005-05-24 17:09 ` James Bottomley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4294972D.4030807@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=ESQuicksall_open_iscsi@Comcast.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=open-iscsi@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox