From: Luben Tuikov <luben_tuikov@adaptec.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: luben_tulkov@adaptec.com,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
Luben Tuikov <luben_tuikov@adaptec.com>
Subject: Re: [PATCH 2.6.13 14/14] sas-class: SCSI Host glue
Date: Mon, 12 Sep 2005 14:46:18 -0400 [thread overview]
Message-ID: <4325CCFA.4060300@adaptec.com> (raw)
In-Reply-To: <1126357713.3222.149.camel@laptopd505.fenrus.org>
Arjan,
You misspelled my email address:
It is not "luben_tulkov@adaptec.com",
It is "luben_tuikov@adatptec.com".
Thanks,
Luben
P.S. I've added a CC to the correct address and left
the mistaken one in.
On 09/10/05 09:08, Arjan van de Ven wrote:
>>No self respecting SAS chip would not do 64 bit DMA, or have an sg tablesize
>>or any other limitation.
>
>
> yet... there will be :)
>
>>Naturally, aic94xx has _no limitations_. :-) But hey, our hardware just
>>kicks a*s!
>
>
> if it has no such limits then it indeed does!
>
>
>
>>(Oh, I know, the solution you're paid to push into the kernel
>>doesn't need those since it does all SAS in the firmware.)
>
>
> I think you are way out of line here. James is very prudent in
> separating his job at SteelEye and his maintainership.
>
>
>
>>Hmm, lets see:
>>I posted today, a _complete_ solution, 1000 years ahead of this
>>"embryonic SAS class" you speak of.
>
>
> yet you post this without having had ANY discussion or earlier reviews
> in the recent months. IN fact to the outside world it looks like you sat
> on this code for a long time for competative reasons and just posted it
> now that Christoph is getting his layer finished.
>
>
>
>>Furthermore, why do you want to use a downgrade solution?
>>
>>The answer is simple:
>> After "emd", Dell (Hi Matt!) learned quickly that if they want something
>>in SCSI Core, they have to hire the people who _make_the_decisions_ what
>>goes in and stays out of SCSI Core, to write that something, irrespectively
>
>
> well EMD's failure was 100% Adaptecs fault. Adaptec was warned EARLY ON
> that a dmraid like solution was going to be needed. It was just that
> Adaptec decided to ignore this advice (and focus only on 2.4 and ignore
> 2.6 entirely) that caused Adaptec to waste all the time and money on it.
>
>
>
>>So as long as *you are on their payroll*, what are you discussing here
>
>
> James is paid by SteelEye. Not by Dell or LSI.
>
>
>>with me? *You have an agenda*!
>
>
> so do you.
>
>
>>I long for the days of the previous maintainer.
>
>
> What previous maintainer?
>
>
>
next prev parent reply other threads:[~2005-09-12 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-09 19:42 [PATCH 2.6.13 14/14] sas-class: SCSI Host glue Luben Tuikov
2005-09-09 23:35 ` James Bottomley
2005-09-10 4:12 ` Luben Tuikov
2005-09-10 13:08 ` Arjan van de Ven
2005-09-12 13:55 ` Luben Tuikov
2005-09-12 14:13 ` Jörn Engel
2005-09-12 18:46 ` Luben Tuikov
2005-09-12 18:46 ` Luben Tuikov [this message]
2005-09-10 14:30 ` Rik van Riel
2005-09-10 20:20 ` Alan Cox
2005-09-11 9:40 ` Christoph Hellwig
2005-09-13 12:41 ` Luben Tuikov
2005-09-11 3:56 ` ak
2005-09-11 13:41 ` James Bottomley
2005-09-12 17:12 ` Luben Tuikov
2005-09-12 17:55 ` Alan Cox
2005-09-12 13:56 ` Luben Tuikov
2005-09-11 9:38 ` Christoph Hellwig
2005-09-12 16:08 ` Matthew Wilcox
2005-09-12 19:07 ` Luben Tuikov
2005-09-12 19:55 ` Matthew Wilcox
2005-09-12 23:51 ` Stefan Richter
2005-09-12 22:00 ` Luben Tuikov
2005-09-13 15:40 ` Matthew Wilcox
2005-09-14 5:56 ` Sergey Panov
2005-09-14 10:37 ` Christoph Hellwig
2005-09-14 10:53 ` Jeff Garzik
2005-09-14 12:59 ` Luben Tuikov
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=4325CCFA.4060300@adaptec.com \
--to=luben_tuikov@adaptec.com \
--cc=James.Bottomley@SteelEye.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tulkov@adaptec.com \
/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).