From: Jeff Garzik <jgarzik@pobox.com>
To: Jens Axboe <axboe@suse.de>
Cc: Daniel Drake <dsd@gentoo.org>, Otto Meier <gf435@gmx.net>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Driver for sata adapter promise sata300 tx4
Date: Mon, 01 Aug 2005 16:49:25 -0400 [thread overview]
Message-ID: <42EE8AD5.6080100@pobox.com> (raw)
In-Reply-To: <20050801204241.GU22569@suse.de>
Jens Axboe wrote:
> On Mon, Aug 01 2005, Jeff Garzik wrote:
>
>>Jens Axboe wrote:
>>
>>>Oh, and forget TCQ. It's a completely worthless technology inherited
>>
>>>from PATA,
>>
>>Agreed.
>>
>>There are a few controllers where we may -eventually- add TCQ support,
>>controllers that do 100% of TCQ in hardware. But that's so far down the
>>priority list, it's below just about everything else.
>>
>>There may just be little motivation to -ever- support TCQ, even when
>>libata is the 'main' IDE driver, sometime in the future.
>
>
> Host supported TCQ only removes the pain from the software side, it
> still doesn't make it a fast techology. The only reason you would want
> to support that would be "it's easy, why not...". From my POV, I would
> refuse to support it just from an ideological standpoint :-)
>
> Legacy TCQ, hell no, not in a million years.
This is largely a confusion of terminology. On the SATA page,
"host-based TCQ" == host controller has a hardware queue (DMA ring, or
whatnot)
"legacy TCQ" == making use of READ/WRITE DMA QUEUED commands.
I would only consider accepting the -intersection- of these two feature
sets, where host TCQ and legacy TCQ are -both- present. As an extremely
low, low priority. :)
As a terminology side note, the SATA community refers to "everything
that is not NCQ" as "legacy TCQ". Legacy TCQ doesn't necessarily imply
use of the standard PCI IDE interface, handling SERV interrupts and all
that nastiness.
Patches to software-status.html to make this more clear are certainly
welcome, as well :)
Jeff
next prev parent reply other threads:[~2005-08-01 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-01 9:19 Driver for sata adapter promise sata300 tx4 Otto Meier
2005-08-01 14:43 ` Daniel Drake
2005-08-01 15:12 ` Otto Meier
2005-08-01 15:28 ` Otto Meier
2005-08-01 16:16 ` Daniel Drake
2005-08-01 20:17 ` Jens Axboe
2005-08-01 20:30 ` Jeff Garzik
2005-08-01 20:35 ` Jens Axboe
2005-08-02 8:18 ` Otto Meier
2005-08-01 20:32 ` Jens Axboe
2005-08-01 20:36 ` Jeff Garzik
2005-08-01 20:42 ` Jens Axboe
2005-08-01 20:49 ` Jeff Garzik [this message]
2005-08-02 6:48 ` 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=42EE8AD5.6080100@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=dsd@gentoo.org \
--cc=gf435@gmx.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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