linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Vladislav Bolkhovitin <vst@vlnb.net>
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: Tue, 17 Aug 2010 15:30:40 -0500	[thread overview]
Message-ID: <1282077040.16098.47.camel@mulgrave.site> (raw)
In-Reply-To: <4C69653E.6050808@vlnb.net>

On Mon, 2010-08-16 at 20:20 +0400, Vladislav Bolkhovitin wrote:
> Hello James,
> 
> Could you comment rumors that decision about future Linux SCSI target 
> subsystem is done as well as other related rumors:

If this is related to LSF, the notes on the I/O track are here:

http://lwn.net/Articles/400491/

> 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".

> 2. Don't you like something in the sysfs interface SCST has?

I don't think so ... from a cursory glance it looks functional.

> 3. I have heard you said "Vlad wasn't comfortable in handing up the 
> control to the maintainers ... (this is how kernel.org works)." I have 
> no idea what you meant. I have never been asked about anything like 
> that, so I couldn't say anyhow that I'm not comfortable with anything. 
> Could you clarify that?
> 
> 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.

James



  reply	other threads:[~2010-08-17 20:30 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 [this message]
2010-08-18 17:52   ` Vladislav Bolkhovitin
2010-08-18 20:43     ` James Bottomley
2010-08-21 18:51       ` Vladislav Bolkhovitin
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=1282077040.16098.47.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=scst-devel@lists.sourceforge.net \
    --cc=vst@vlnb.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;
as well as URLs for NNTP newsgroup(s).