From: "Tomi Orava" <Tomi.Orava@ncircle.nullnet.fi>
To: "Jens Axboe" <axboe@suse.de>
Cc: "Bartlomiej Zolnierkiewicz" <b.zolnierkiewicz@elka.pw.edu.pl>,
"Andre Hedrick" <andre@linux-ide.org>,
"Svetoslav Slavtchev" <svetljo@gmx.de>,
linux-kernel@vger.kernel.org
Subject: Re: HighPoint 374
Date: Mon, 20 Oct 2003 10:43:33 +0300 (EEST) [thread overview]
Message-ID: <17073.194.237.142.24.1066635813.squirrel@ncircle.nullnet.fi> (raw)
In-Reply-To: <20031020064831.GT1128@suse.de>
> On Sun, Oct 19 2003, Bartlomiej Zolnierkiewicz wrote:
>>
>> Andre, thanks for helpful hint.
>> Svetoslav, the right person to whine about TCQ stuff is Jens Axboe 8-).
>
> Well that's correct, but this looks more like an AS iosched bug :)
Pardon my ignorance, but what is this AS iosched ?
>> > You do not enable TCQ on highpoint without using the hosted polling
>> timer.
>> > Oh and I have not added it, and so hit Bartlomiej up for the
>> additions.
>
> For what? TCQ tests fine on a HPT370 here.
I'm not entirely sure if that proves something or not,
as the whole (interrupt & hang) problem seems to exist
only with HPT374 and not with any other version of the chip anyway.
I do personally have one mb with a 372-chip and it has always
worked just fine with this same driver (perhaps its harder
to detect the problem with only two disks?).
Regards,
Tomi Orava
next prev parent reply other threads:[~2003-10-20 7:43 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 19:57 Svetoslav Slavtchev
2003-10-19 20:30 ` Andre Hedrick
2003-10-19 20:46 ` Svetoslav Slavtchev
2003-10-19 20:51 ` Bartlomiej Zolnierkiewicz
2003-10-19 20:54 ` Svetoslav Slavtchev
2003-10-20 6:48 ` Jens Axboe
2003-10-20 7:43 ` Tomi Orava [this message]
2003-10-20 8:10 ` Svetoslav Slavtchev
2003-10-20 8:21 ` Nick Piggin
2003-10-20 8:30 ` Svetoslav Slavtchev
2003-10-19 21:51 ` Tomi Orava
2003-10-19 22:00 ` Svetoslav Slavtchev
2003-10-19 22:11 ` Svetoslav Slavtchev
2003-10-19 22:24 ` Tomi Orava
2003-10-20 7:53 ` Svetoslav Slavtchev
2003-10-20 8:03 ` Tomi Orava
2003-10-20 9:03 ` Svetoslav Slavtchev
2003-10-20 17:02 ` Carlos Fernandez Sanz
2003-10-20 19:14 ` Svetoslav Slavtchev
2003-10-20 20:23 ` Carlos Fernandez Sanz
2003-10-20 21:07 ` Svetoslav Slavtchev
2003-10-20 21:25 ` Bartlomiej Zolnierkiewicz
2003-10-20 21:25 ` Svetoslav Slavtchev
2003-10-21 18:43 ` Tomi Orava
2003-10-21 18:50 ` Tomi Orava
-- strict thread matches above, loose matches on Subject: below --
2003-10-21 9:23 Jindrich Makovicka
2003-10-21 16:59 ` Tomi Orava
2003-10-19 19:42 Christian Guggenberger
2003-10-19 19:54 ` Tomi Orava
2003-10-18 9:44 Carlos Fernandez Sanz
2003-10-18 10:15 ` Måns Rullgård
2003-10-19 12:13 ` Tomi Orava
2003-10-19 16:48 ` Carlos Fernandez Sanz
2003-10-19 17:16 ` Tomi Orava
2003-10-19 17:39 ` Carlos Fernandez Sanz
2003-10-19 19:27 ` Tomi Orava
2003-10-19 19:35 ` Carlos Fernandez Sanz
2003-10-19 15:59 ` Joel Smith
2003-10-19 17:24 ` Tomi Orava
2003-10-19 17:42 ` Måns Rullgård
2003-10-19 19:14 ` Tomi Orava
2003-10-19 19:27 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Tomi Orava
2003-10-19 20:12 ` Carlos Fernandez Sanz
2003-10-19 19:39 ` Måns Rullgård
2003-10-19 19:54 ` David B. Stevens
2003-10-20 8:38 ` Geller Sandor
2003-10-19 21:12 ` Joel Smith
2003-10-19 17:28 ` Carlos Fernandez Sanz
2003-10-19 21:35 ` Joel Smith
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=17073.194.237.142.24.1066635813.squirrel@ncircle.nullnet.fi \
--to=tomi.orava@ncircle.nullnet.fi \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=b.zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=svetljo@gmx.de \
/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®