From: Andre Hedrick <andre@linux-ide.org>
To: "Mudama, Eric" <eric_mudama@maxtor.com>
Cc: Jens Axboe <axboe@suse.de>, Jeff Garzik <jgarzik@pobox.com>,
Dave Jones <davej@codemonkey.org.uk>,
Oleg Drokin <green@namesys.com>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Oliver Neukum <oliver@neukum.org>,
lkhelp@rekl.yi.org, linux-kernel@vger.kernel.org
Subject: RE: 2.5.69, IDE TCQ can't be enabled
Date: Tue, 13 May 2003 13:34:44 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10305131329390.2718-100000@master.linux-ide.org> (raw)
In-Reply-To: <785F348679A4D5119A0C009027DE33C102E0D346@mcoexc04.mlm.maxtor.com>
Correct no drives shipped.
Maxtor failed to move forward in updating the device side TCQ.
I will have to look up my email record to give you who I was working with
and talking to about the issues. I do know it was in the Longmont
division.
The last discussion I had with Maxtor releated in forcing the state
machine to default to bus release on execution of the command block.
This would fix the the gaping hole in the protocol. The effects from this
single change were not fully white board material, and may have addressed
or covered the other two pitfalls.
Drop the ball, meaning it was started and then tabled.
Tabled because of SATA/SAS.
Comments?
Andre Hedrick
LAD Storage Consulting Group
On Tue, 13 May 2003, Mudama, Eric wrote:
>
>
> -----Original Message-----
> >From: Andre Hedrick [mailto:andre@linux-ide.org]
> >Sent: Tuesday, May 13, 2003 2:04 PM
> >To: Jens Axboe
> >Cc: Jeff Garzik; Dave Jones; Mudama, Eric; Oleg Drokin; Bartlomiej
> >Zolnierkiewicz; Alan Cox; Oliver Neukum; lkhelp@rekl.yi.org;
> >linux-kernel@vger.kernel.org
> >Subject: Re: 2.5.69, IDE TCQ can't be enabled
> >
> >Why are we still dorking around with device TCQ.
> >There are three holes in the state machine.
> >IBM's design (goat-screw) is lamer than a duck.
> >Maxtor thought about redoing TCQ, to not leave the host in a daze but
> >dropped the ball.
>
> What ball, exactly, did we drop? We have yet to ship a TCQ drive because we
> think we can get it "right" but it is taking us time, in our view, to do
> properly.
>
> --eric
>
next prev parent reply other threads:[~2003-05-13 20:29 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-13 20:31 2.5.69, IDE TCQ can't be enabled Mudama, Eric
2003-05-13 20:34 ` Andre Hedrick [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 20:43 Mudama, Eric
2003-05-13 20:28 Mudama, Eric
2003-05-12 19:19 Mudama, Eric
2003-05-12 19:35 ` Jeff Garzik
2003-05-12 19:42 ` Jens Axboe
2003-05-12 19:44 ` Jens Axboe
2003-05-12 19:53 ` Jeff Garzik
2003-05-13 6:40 ` Jens Axboe
2003-05-13 18:00 ` Dave Jones
2003-05-13 18:03 ` Jens Axboe
2003-05-13 18:05 ` Jeff Garzik
2003-05-13 18:06 ` Jens Axboe
2003-05-13 18:13 ` Jens Axboe
2003-05-13 18:42 ` Jeff Garzik
2003-05-13 20:29 ` Andre Hedrick
2003-05-14 7:04 ` Jens Axboe
2003-05-14 7:15 ` Jens Axboe
2003-05-13 20:03 ` Andre Hedrick
2003-05-13 22:55 ` Alan Cox
2003-05-13 18:03 ` Jeff Garzik
2003-05-14 13:30 ` Henning P. Schmiedehausen
2003-05-12 22:36 ` Christer Weinigel
2003-05-13 6:41 ` Jens Axboe
2003-05-13 20:04 ` Bill Davidsen
2003-05-12 17:58 Mudama, Eric
2003-05-12 18:59 ` Jens Axboe
2003-05-12 19:42 ` Jeff Garzik
2003-05-10 1:38 lkhelp
2003-05-12 12:46 ` Oleg Drokin
2003-05-12 12:55 ` Oliver Neukum
2003-05-12 13:16 ` Bartlomiej Zolnierkiewicz
2003-05-12 13:12 ` Alan Cox
2003-05-13 15:39 ` Jens Axboe
2003-05-12 13:22 ` Oleg Drokin
2003-05-12 13:23 ` Jens Axboe
2003-05-12 13:35 ` Jeff Garzik
2003-05-12 13:30 ` Bartlomiej Zolnierkiewicz
2003-05-12 13:22 ` Jens Axboe
2003-05-13 15:32 ` Jens Axboe
2003-05-13 17:25 ` Oliver Neukum
2003-05-13 17:28 ` Jens Axboe
2003-05-13 18:46 ` Oliver Neukum
2003-05-13 19:06 ` Jens Axboe
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=Pine.LNX.4.10.10305131329390.2718-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=davej@codemonkey.org.uk \
--cc=eric_mudama@maxtor.com \
--cc=green@namesys.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkhelp@rekl.yi.org \
--cc=oliver@neukum.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).