From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: IDE TCQ progress?
Date: Tue, 21 Jan 2003 10:37:40 +0100 [thread overview]
Message-ID: <200301211037.40872.roy@karlsbakk.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0301201907370.8486-100000@coffee.psychology.mcmaster.ca>
> is it safe to assume you have TCQ-able drives? last time I asked
> the maintainer, there were only a few WD Caviar's that did it.
As specified in the config docs
bool "ATA tagged command queueing (EXPERIMENTAL)"
depends on BLK_DEV_IDEDMA_PCI && 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
supports it. For now this includes the IBM Deskstar series drives,
such as the 22GXP, 75GXP, 40GV, 60GXP, and 120GXP (ie any Deskstar
made
in the last couple of years), and at least some of the Western
Digital drives in the Expert series (by nature of really being IBM
drives).
If you have such a drive, say Y here.
I've got an IBM 120GXP (IC35L060AVVA07-0)
> second, what were you expecting? the kernel already schedules the head,
> so the only time it should matter is if you're doing a lot of writes
> in a particular sequence of block addresses in the same cylinder.
I expected the kernel to be somehow stable. Not too much more.
I have heard, however, that TCQ'll help a lot if connecting > 1 unit to the
same IDE bus. Is this true?
roy
--
Roy Sigurd Karlsbakk, Datavaktmester
ProntoTV AS - http://www.pronto.tv/
Tel: +47 9801 3356
Computers are like air conditioners.
They stop working when you open Windows.
next parent reply other threads:[~2003-01-21 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0301201907370.8486-100000@coffee.psychology.mcmaster.ca>
2003-01-21 9:37 ` Roy Sigurd Karlsbakk [this message]
2003-01-20 14:52 Roy Sigurd Karlsbakk
2003-01-21 9:27 ` Morten Helgesen
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=200301211037.40872.roy@karlsbakk.net \
--to=roy@karlsbakk.net \
--cc=hahn@physics.mcmaster.ca \
--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®