public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Mattie <codermattie@gmail.com>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: htpt366 PCI latency value is really high
Date: Thu, 26 Apr 2007 06:49:27 -0700	[thread overview]
Message-ID: <20070426064927.13d0ed72@reforged> (raw)

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

Hello,

while hunting down some latency problems I found something quite odd.
The latency reported by lspci -v for the HTP203N card is enormous.

00:09.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N
(rev 02) Subsystem: Triones Technologies, Inc. Unknown device 0001
        Flags: bus master, 66MHz, medium devsel, latency 120, IRQ 17
        I/O ports at ec00 [size=8]
        I/O ports at e800 [size=4]
        I/O ports at e400 [size=8]
        I/O ports at e000 [size=4]
        I/O ports at dc00 [size=256]
        Expansion ROM at dffe0000 [disabled by cmd] [size=128K]
        Capabilities: [60] Power Management version 2


I am assuming that the "latency" field here is the PCI latency timer
which means this card is a bus hog. 

From some reading on this issue linux methodically sets a sane value for 
all the PCI cards it sets up, which looks normal on the rest of the system, 
which is set to the value: 32

setting the value 32 with:

setpci -v -s "00:09.0" latency_timer=32

00:09.0 RAID bus controller: Triones Technologies, Inc. HPT302/302N (rev 02)
        Subsystem: Triones Technologies, Inc. Unknown device 0001
        Flags: bus master, 66MHz, medium devsel, latency 48, IRQ 17
        I/O ports at ec00 [size=8]
        I/O ports at e800 [size=4]
        I/O ports at e400 [size=8]
        I/O ports at e000 [size=4]
        I/O ports at dc00 [size=256]
        Expansion ROM at dffe0000 [disabled by cmd] [size=128K]
        Capabilities: [60] Power Management version 2

Results in 48, which is not what I asked, but hopefully this is
linux doing the right thing.

I know this chipset is pretty brain-damaged, but is this
high latency value a work-around for broken hardware, or
just a oversight ?

Cheers,
Mike Mattie - codermattie@gmail.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-04-26 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-26 13:49 Mike Mattie [this message]
2007-04-26 14:30 ` htpt366 PCI latency value is really high Sergei Shtylyov
2007-04-28  6:09   ` Mike Mattie
2007-04-28  9:48     ` Alan Cox
2007-04-28 13:01       ` Sergei Shtylyov

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=20070426064927.13d0ed72@reforged \
    --to=codermattie@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.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