[<prev] [next>] [day] [month] [year] [list]
Message-ID: <AANLkTinARwxMat+YA0XsKTozdvh5Tta8_CDhZ8bM-NMa@mail.gmail.com>
Date: Wed, 18 Aug 2010 17:30:33 +0200
From: Bart Van Assche <bvanassche@....org>
To: James Bottomley <James.Bottomley@...e.de>
Cc: Chetan Loke <generationgnu@...oo.com>,
Vladislav Bolkhovitin <vst@...b.net>,
scst-devel <scst-devel@...ts.sourceforge.net>,
linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [Scst-devel] Fwd: Re: linuxcon 2010...
On Wed, Aug 18, 2010 at 5:11 PM, James Bottomley
<James.Bottomley@...e.de> wrote:
>
> On Wed, 2010-08-18 at 07:58 -0700, Chetan Loke wrote:
> > [ ... ]
> >
> > During the open panel, my question was really specific -
> >
> > Q) What is the future of a SCSI-target subsystem in linux. Which
> > target engine/subsystem can we expect?
> >
> > Your answer) There is place for only 1 target-subsystem in the Linux
> > scsi stack and in the LSF summit the decision was taken to merge LIO.
> > Has that
> > decision changed since the summit?
>
> The decision hasn't been taken to merge LIO, but based on what happened
> at the summit, I think it's the most viable candidate and will likely be
> merged by 2.6.37
(resending as plain text)
No matter which kernel-based storage target subsystem is merged, a
migration path should be provided for SCST users such that these can
continue using their SCST target drivers without too much trouble.
Otherwise you'll upset a large number of SCST users.
Note: an SCST target driver is the code that implements a storage
protocol. See also http://scst.sourceforge.net/scst_pg.html for a
overview diagram.
Bart.
--
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