From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
"Mudama, Eric" <eric_mudama@maxtor.com>,
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: Wed, 14 May 2003 09:15:58 +0200 [thread overview]
Message-ID: <20030514071558.GX17033@suse.de> (raw)
In-Reply-To: <20030513184205.GC11073@gtf.org>
On Tue, May 13 2003, Jeff Garzik wrote:
> On Tue, May 13, 2003 at 08:13:37PM +0200, Jens Axboe wrote:
> > btw, you may want to see the IDE_TCQ_FIDDLE_SI define in ide-tcq, here's
> > the comment I put there:
> >
> > /*
> > * we are leaving the SERVICE interrupt alone, IBM drives have it
> > * on per default and it can't be turned off. Doesn't matter, this
> > * is the sane config.
> > */
> > #undef IDE_TCQ_FIDDLE_SI
> >
> > Are you sure this isn't what you are seeing?
>
>
> My information comes solely from IDENTIFY DEVICE...
Maybe you shouldn't trust that, then :-)
Seriously, I suppose it depends on the drive or maybe that IBM
interprets the bits differently. This puppy:
IC35L040AVVA07-0
says it doesn't support it either, but I can damn well assure you that
it does. What it doesn't support (like other IBM's) is trying to change
it, then it complains.
So I'd be willing to bet lots of money that you drive generates service
interrupts just fine. As I said, I've yet to see one that doesn't.
--
Jens Axboe
next prev parent reply other threads:[~2003-05-14 7:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 19:19 2.5.69, IDE TCQ can't be enabled 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2003-05-13 20:43 Mudama, Eric
2003-05-13 20:31 Mudama, Eric
2003-05-13 20:34 ` Andre Hedrick
2003-05-13 20:28 Mudama, Eric
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=20030514071558.GX17033@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--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).