From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: "Daniel Blueman" <daniel.blueman@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: File system performance, hardware performance, ext3, 3ware RAID1, etc.
Date: Fri, 13 Feb 2004 17:15:33 +0100 [thread overview]
Message-ID: <200402131715.33710.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <17899.1076683453@www11.gmx.net>
On Friday 13 of February 2004 15:44, Daniel Blueman wrote:
> It is a small loss that the TCQ-support implementation hasn't been stable
> on linux so far. I guess mostly due to the great I/O scheduling Linux has
> (ie anticipatory scheduler).
>
> Yes, a growing number of IDE disk manufacturers are using native S-ATA
> controllers in their disks, and TCQ is one of the core features (ie unique
> selling point), as well as being implemented on the more lavish P-ATA
> controllers.
Ugh, you are messing PATA drive TCQ, PATA host TCQ and SATA TCQ.
> It's just a shame that there are still issues saturating a bunch of IDE
> disks with software RAID in the 2.6 series, but I guess that'll be ironed
> out in time...
>
> > Daniel Blueman wrote:
> > > many modern IDE disks and
> > > controllers also have tagged command queuing, so it is even more of a
> >
> > corner case.
> >
> > Linux doesn't use tagged command queueing, though - the code has been
> > disabled for some time. I thought the TCQ stuff was disabled because
> > only very few disks supported it and the code wasn't reliable.
You can re-enable it quite simply 8).
--- Kconfig.orig 2004-02-10 16:29:19.000000000 +0100
+++ Kconfig 2004-02-13 17:06:57.628617096 +0100
@@ -441,7 +441,7 @@
# TCQ is disabled for now
config BLK_DEV_IDE_TCQ
bool "ATA tagged command queueing (EXPERIMENTAL)"
- depends on EXPERIMENTAL && n
+ depends on EXPERIMENTAL
help
Support for tagged command queueing on ATA disk drives. This enables
the IDE layer to have multiple in-flight requests on hardware that
> > Yet you say many modern disks support it?
No, only IBM/Hitachi and some WD disks support IDE TCQ.
next prev parent reply other threads:[~2004-02-13 16:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 12:23 Daniel Blueman
2004-02-13 14:27 ` Jamie Lokier
2004-02-13 14:44 ` Daniel Blueman
2004-02-13 16:15 ` Bartlomiej Zolnierkiewicz [this message]
2004-02-13 22:56 ` Timothy Miller
-- strict thread matches above, loose matches on Subject: below --
2004-02-14 18:16 Walt H
2004-02-16 17:53 ` Timothy Miller
2004-02-12 23:32 Timothy Miller
2004-02-13 5:53 ` Willy Tarreau
2004-02-13 19:19 ` Timothy Miller
2004-02-13 22:39 ` Willy Tarreau
2004-02-13 23:14 ` Timothy Miller
2004-02-13 19:30 ` Eric D. Mudama
2004-02-13 19:55 ` Linus Torvalds
2004-02-13 20:44 ` John Bradford
2004-02-13 22:45 ` Willy Tarreau
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=200402131715.33710.bzolnier@elka.pw.edu.pl \
--to=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=daniel.blueman@gmx.net \
--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
all inboxes | Powered by JetHome®