From: Vladislav Bolkhovitin <vst@vlnb.net>
To: chetan loke <loke.chetan@gmail.com>
Cc: James Bottomley <James.Bottomley@suse.de>,
"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>,
Bart Van Assche <bart.vanassche@gmail.com>
Subject: Re: [ANNOUNCE] TCM/LIO v4.0.0-rc6 for 2.6.37-rc6
Date: Wed, 22 Dec 2010 18:28:00 +0300 [thread overview]
Message-ID: <4D121900.2000404@vlnb.net> (raw)
In-Reply-To: <AANLkTimV-evsF4MFXs6JQ5H55AgtOpGrTuCdJBx9O_P=@mail.gmail.com>
chetan loke, on 12/18/2010 10:13 PM wrote:
> On Fri, Dec 17, 2010 at 4:35 PM, Vladislav Bolkhovitin <vst@vlnb.net> wrote:
>>
>> In this regard it looks to be a good idea to freeze accepting both LIO
>> and SCST until the end of the next year and then choose one with the
>> biggest activity in the related mailing lists, not counting me and
>> NicholasB.
>
> Why wait till the end of the next year? What I proposed earlier was
> 'to review at the architecture level'. If folks don't agree to it then
> this email drama will never
> stop. Once the review starts we can decide on a common baseline to
> benchmark both the stacks. I'm more than willing to test/benchmark
> ESX(front-end)/SCST/LIO(back-end) combo. I'm sure there will be others
> who would be willing to spend some of their time for this cause to
> validate claims made by both the communities. We can then publish all
> the results so that others can reproduce them.
This will be exactly what we need: an open and fair comparison. But the
problem is that James doesn't want any comparisons. He doesn't consider
them important. Only personality of the code submitter is important for
James.
Vlad
next prev parent reply other threads:[~2010-12-22 15:29 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
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 [this message]
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=4D121900.2000404@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@suse.de \
--cc=bart.vanassche@gmail.com \
--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=loke.chetan@gmail.com \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--cc=torvalds@linux-foundation.org \
--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).