From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dmitry Yusupov <dmitry_yus@yahoo.com>
Cc: Luben Tuikov <luben_tuikov@adaptec.com>,
open_iscsi <ESQuicksall_open_iscsi@Comcast.net>,
Mike Christie <michaelc@cs.wisc.edu>,
'SCSI Mailing List' <linux-scsi@vger.kernel.org>,
open-iscsi@googlegroups.com
Subject: Re: [PATCH RFC 2/2] implement transport scan callout for iscsi
Date: Wed, 25 May 2005 15:42:34 -0400 [thread overview]
Message-ID: <1117050154.4760.1.camel@mulgrave> (raw)
In-Reply-To: <1117045931.16262.149.camel@beastie>
On Wed, 2005-05-25 at 11:32 -0700, Dmitry Yusupov wrote:
> Those are very strong arguments against having MC/S implemented for the
> software iSCSI initiator. Especially true is (a). Not that many targets
> offers MC/S, since according to RFC it implies ERL=2.
>
> Now, back to open-iscsi initiator business and its mainline acceptance.
> We are going to met your requirement and will remove multi-connection
> support before next patch-set submission. As Mike C. mentioned before,
> it is fairly easy to do since the whole connection management resides in
> user-space. Though it will exists as a kernel patches on our web site
> (http://www.open-iscsi.org) for those who wonders.
>
> Are there are some other requirements we need to met besides MC/S
> removal ?
Actually, I don't think so. I'd like some convergence on what should be
in the transport class, since there have been a set of conflicting
patches from Mike Christie and Nicholas Bellinger, but that's not a
requirement ... what's there already can go in and we can sort out the
residue in-tree.
James
next prev parent reply other threads:[~2005-05-25 20:54 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
2005-05-25 18:04 ` James Bottomley
2005-05-25 18:32 ` Dmitry Yusupov
2005-05-25 19:42 ` James Bottomley [this message]
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=1117050154.4760.1.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=ESQuicksall_open_iscsi@Comcast.net \
--cc=dmitry_yus@yahoo.com \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--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