From: Vladislav Bolkhovitin <vst@vlnb.net>
To: James Bottomley <James.Bottomley@suse.de>
Cc: scst-devel <scst-devel@lists.sourceforge.net>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: [Scst-devel] linuxcon 2010...
Date: Sat, 21 Aug 2010 22:51:28 +0400 [thread overview]
Message-ID: <4C702030.2070306@vlnb.net> (raw)
In-Reply-To: <1282164188.10878.22.camel@mulgrave.site>
James Bottomley, on 08/19/2010 12:43 AM wrote:
>>>> 1. What don't you like in the transition path for users from STGT to
>>>> SCST, which I proposed:
>>>>
>>>> - The only people which would be affected by replacing of STGT by SCST
>>>> would be users of ibmvstgt. Other STGT users would not notice it at all.
>>>> Thus, we should update ibmvstgt for SCST. If ibmvstgt updated for SCST,
>>>> the update for its users would be just writing of a simple scstadmin's
>>>> config file.
>>>>
>>>> - STGT doesn't have backend drivers, which SCST doesn't have, so
>>>> there's nothing to worry here. At max, AIO support should be added to
>>>> fileio_tgt.
>>>>
>>>> - STGT user space targets can use SCST backend via scst_local module.
>>>> Scst_local module is ready and work very well.
>>>>
>>>> The result would be very clear without any obsolete mess.
>>>
>>> So does that get us up to being a drop in replacement? I think you're
>>> saying that even with all of this, at least the VSCSI part will need
>>> updating, so the answer seems to be "no".
>>
>> Sorry, I can't understand, "no" for which? For the whole transition
>> path, or just until there is a patch for ibmvstgt to become ibmvscst?
>
> No to the question "does that get us up to being a drop in replacement
> [for STGT]?"
I'm sorry again, I did my best, but still can't understand. What you
wrote looks for me too ambiguous. My English must be too bad..
Could elaborate more for what the "no" is, please? What don't you like
in the plan I suggested?
>>>> 4. Have you changed your opinion that a driver level multipath is
>>>> forbidden in Linux and now you think that an iSCSI target with MC/S
>>>> support is acceptable?
>>>
>>> no; I still think MCS is a pointless duplication of multipath that only
>>> works for iSCSI.
>>
>> Then, does it mean that similarly as it was with open-iscsi, which had
>> to remove MC/S support to be able to be accepted into the mainline, an
>> iSCSI target can't go into mainline if it has MC/S?
>
> To be honest, I don't care about targets. I only care that the
> initiators do the right thing.
Isn't it quite illogical? You are forbidding a facility on one side of
the link and allow it on another?
Thanks,
Vlad
next prev parent reply other threads:[~2010-08-21 18:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 16:20 Fwd: Re: [Scst-devel] linuxcon 2010 Vladislav Bolkhovitin
2010-08-17 20:30 ` James Bottomley
2010-08-18 17:52 ` Vladislav Bolkhovitin
2010-08-18 20:43 ` James Bottomley
2010-08-21 18:51 ` Vladislav Bolkhovitin [this message]
2010-08-21 20:38 ` James Bottomley
2010-08-22 22:10 ` [Scst-devel] Fwd: " Gennadiy Nerubayev
2010-08-23 16:59 ` James Bottomley
2010-08-23 17:44 ` Bart Van Assche
2010-08-23 17:58 ` James Bottomley
2010-08-23 20:11 ` Bart Van Assche
2010-08-23 20:21 ` James Bottomley
2010-08-23 19:40 ` Vladislav Bolkhovitin
2010-08-23 20:38 ` James Bottomley
2010-08-24 10:32 ` Bart Van Assche
2010-08-24 13:01 ` Chris Weiss
2010-08-24 19:53 ` Vladislav Bolkhovitin
2010-08-23 19:40 ` Vladislav Bolkhovitin
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=4C702030.2070306@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=scst-devel@lists.sourceforge.net \
/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