From: Mike Fedyk <mfedyk@matchmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Greg Stark <gsstark@mit.edu>, Erik Steffl <steffl@bigfoot.com>,
linux-kernel@vger.kernel.org
Subject: Re: libata in 2.4.24?
Date: Tue, 2 Dec 2003 10:46:48 -0800 [thread overview]
Message-ID: <20031202184648.GU1566@mis-mike-wstn.matchmail.com> (raw)
In-Reply-To: <20031202180458.GC1990@gtf.org>
On Tue, Dec 02, 2003 at 01:04:58PM -0500, Jeff Garzik wrote:
> On Tue, Dec 02, 2003 at 09:40:48AM -0800, Mike Fedyk wrote:
> > There are PATA drives that do TCQ too, but you have to look for that feature
> > specifically. IDE TCQ is in 2.6, but is still experemental. I think Jens
> > Axboe was the one working on it IIRC. He would have more details.
>
> Let us distinguish three types of TCQ:
> 1) PATA drive-side TCQ (now called "legacy TCQ")
> 2) Controller-side TCQ
> 3) SATA drive/controller-side TCQ ("first party DMA")
>
> libata will never support #1, which is what 2.6 supports in experimental
> option.
An experemental option with the ide layer, not libata, right?
>
> libata will support #2 very soon, and will support #3 when hardware is
> available.
>
If you have Controller-side TCQ, then will it work with any IDE PATA/SATA
drive?
> > > Do the new SATA drives and controllers provide a solution to this?
> >
> > It's not SATA specific, and I'm not sure if any ide controller can support
> > TCQ or if only a specific list are compatible.
>
> The TCQ you are thinking of has been deprecated by the people who make
> IDE drives ;-)
Ahh, it's good to know that our TCQ support isn't lagging. We're even
supporting TCQ standards that were only in place for 1 or 2 years. :)
next prev parent reply other threads:[~2003-12-02 18:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 18:27 linux-2.4.23 released Marcelo Tosatti
2003-11-28 19:06 ` Willy Tarreau
2003-11-28 22:55 ` J.A. Magallon
2003-11-29 22:26 ` libata in 2.4.24? Samuel Flory
2003-11-29 23:10 ` Marcelo Tosatti
2003-12-01 10:43 ` Marcelo Tosatti
2003-12-01 18:06 ` Samuel Flory
2003-12-01 21:12 ` Greg Stark
2003-12-01 21:23 ` Samuel Flory
2003-12-01 21:44 ` Greg Stark
2003-12-01 22:00 ` Jeff Garzik
2003-12-01 22:06 ` Samuel Flory
2003-12-01 22:00 ` Erik Steffl
2003-12-02 5:36 ` Greg Stark
[not found] ` <20031202055336.GO1566@mis-mike-wstn.matchmail.com>
2003-12-02 5:58 ` Mike Fedyk
2003-12-02 16:31 ` Greg Stark
2003-12-02 17:40 ` Mike Fedyk
2003-12-02 18:04 ` Jeff Garzik
2003-12-02 18:46 ` Mike Fedyk [this message]
2003-12-02 18:49 ` Jeff Garzik
2003-12-04 8:18 ` Jens Axboe
2003-12-02 18:02 ` Jeff Garzik
2003-12-02 18:51 ` Greg Stark
2003-12-02 19:06 ` Jeff Garzik
2003-12-02 20:10 ` Greg Stark
2003-12-02 20:16 ` Jeff Garzik
2003-12-02 20:34 ` Greg Stark
2003-12-02 22:34 ` bill davidsen
2003-12-02 23:02 ` Mike Fedyk
2003-12-02 23:18 ` bill davidsen
2003-12-02 23:40 ` Mike Fedyk
2003-12-03 0:01 ` Jeff Garzik
2003-12-03 0:47 ` Jamie Lokier
2003-12-07 5:33 ` Bill Davidsen
2003-12-01 21:36 ` Justin Cormack
2003-12-01 13:41 Xose Vazquez Perez
2003-12-01 14:11 ` Marcelo Tosatti
2003-12-02 19:59 ` Stephan von Krawczynski
2003-12-02 22:05 ` bill davidsen
2003-12-02 22:34 ` Jeff Garzik
2003-12-03 0:34 Xose Vazquez Perez
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=20031202184648.GU1566@mis-mike-wstn.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=gsstark@mit.edu \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=steffl@bigfoot.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
all inboxes | Powered by JetHome®