From: James Bottomley <James.Bottomley@suse.de>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
"Patil, Kiran" <kiran.patil@intel.com>,
Mike Christie <michaelc@cs.wisc.edu>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Hannes Reinecke <hare@suse.de>,
Boaz Harrosh <bharrosh@panasas.com>,
Joe Eykholt <jeykholt@cisco.com>, "J.H." <warthog9@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [ANNOUNCE] TCM/LIO v4.0.0-rc6 for 2.6.37-rc6
Date: Fri, 17 Dec 2010 11:21:48 -0500 [thread overview]
Message-ID: <1292602908.2820.41.camel@mulgrave.site> (raw)
In-Reply-To: <4D0B8975.1040206@vlnb.net>
On Fri, 2010-12-17 at 19:01 +0300, Vladislav Bolkhovitin wrote:
> James Bottomley, on 12/17/2010 06:22 PM wrote:
> > OK, I think this has reached the stage where it's been polished enough
> > outside mainline to the point where we can complete any remaining todo
> > items in-tree.
> >
> > So lets begin merging with the minimal target core and the TCM_Loop as
> > two separate commits. I think the target core may just fit under the
> > reflector mail length limits, but if not, you can send it as multiple
> > patches and I'll recombine them.
>
> Well, could somebody eventually explain what are advantages of LIO over
> SCST so you are choosing it?
>
> LIO is obviously worse all technically (see
> http://scst.sourceforge.net/comparison.html) as well as in the number of
> users and size of the community. Current in-rush attempts to make LIO
> _look_ not worse than SCST changed nothing in this area.
To be honest, I don't really give a toss about niche feature
comparisons: both products have niche features the other doesn't. The
basic requirements in both products are solid. If the niche feature has
customer value, my estimation is that it can easily be added (to either
product).
> In the resent threads how many people voted for LIO? Nobody. How many
> for SCST? Many. Moreover, has any real user of LIO participated in those
> threads? None?
This isn't a democracy ... it's about choosing the most community
oriented code base so that it's easily maintainable and easy to add
feature requests and improvements as and when they come along. In the
past six months, LIO has made genuine efforts to clean up its act,
streamline its code and support the other community projects that would
need to go above and around it. You seem to have spent a lot of the
intervening time arguing with the sysfs maintainer about why you're
right and he's wrong.
James
> Doesn't that matter for you? Which code is the best doesn't matter for
> Linux anymore?
>
> Undercover games are going on?
>
> Vlad
next prev parent reply other threads:[~2010-12-17 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 3:47 [ANNOUNCE] TCM/LIO v4.0.0-rc6 for 2.6.37-rc6 Nicholas A. Bellinger
2010-12-17 15:22 ` James Bottomley
2010-12-17 16:01 ` Vladislav Bolkhovitin
2010-12-17 16:21 ` James Bottomley [this message]
2010-12-17 19:47 ` Vladislav Bolkhovitin
2010-12-17 20:27 ` James Bottomley
2010-12-17 21:35 ` Vladislav Bolkhovitin
2010-12-17 23:26 ` James Bottomley
2010-12-18 9:15 ` Bart Van Assche
2010-12-18 15:16 ` Vladislav Bolkhovitin
2010-12-18 16:41 ` James Bottomley
2010-12-22 15:26 ` Vladislav Bolkhovitin
2010-12-18 19:13 ` chetan loke
2010-12-22 15:28 ` Vladislav Bolkhovitin
2010-12-18 9:32 ` Bart Van Assche
2010-12-18 18:57 ` chetan loke
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=1292602908.2820.41.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=hpa@zytor.com \
--cc=jeykholt@cisco.com \
--cc=kiran.patil@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=torvalds@linux-foundation.org \
--cc=vst@vlnb.net \
--cc=warthog9@kernel.org \
/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).