linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: RE: raid0 low performance
Date: Tue, 05 Jul 2005 09:19:47 -0400	[thread overview]
Message-ID: <1120569587.5535.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1120523217.5459.20.camel@localhost.localdomain>

Hi,

With this

-[00]-+-00.0  8086:2578
      +-03.0-[01]----01.0  8086:1075
      +-1c.0-[02]--+-01.0  11ab:5081
      |            +-03.0  9005:00c0
      |            +-03.1  9005:00c0
      |            \-04.0  11ab:5041
      +-1e.0-[03]--+-09.0  1002:4752
      |            \-0a.0  8086:1076
      +-1f.0  8086:25a1
      +-1f.1  8086:25a2
      +-1f.2  8086:25a3
      \-1f.3  8086:25a4

i tried to tune the latency-timer on 02:01.0 02:04.0 and 00:1c.0
individually or both. tried 40, 60, 80. no luck.

so i think it is the driver or card fault. :) thanks anyway.

ming

On Mon, 2005-07-04 at 20:26 -0400, Ming Zhang wrote:
> On Mon, 2005-07-04 at 20:13 -0400, Mark Hahn wrote:
> > > # ./lspci -vv -d 11ab:
> > > 02:01.0 Class 0100: 11ab:5081 (rev 03)
> > >         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
> > > ParErr- Stepping- SERR- FastB2B-
> > >         Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> > > <TAbort- <MAbort- >SERR- <PERR-
> > >         Latency: 32, cache line size 08
> > 
> > latency 32 is quite low; this parameter effects how long the device
> > can hold onto the bus.  try
> > 	setpci -s 02:01.0 latency_timer=80
> 
> thanks a lot for this and i will test it tomorrow.
> 
> > and see whether it improves things.  I'm unclear on whether a bridged device
> > also needs the bridge's latency setting changed.
> > 
> > >         Latency: 32, cache line size 08
> > 
> > also low.  I'm guessing that your bios is tuned for desktop use - some audio
> > setups need low latency settings.
> > 
> yes, i guess so, the only drawback of this box is that i am using a
> entry level server box. so its chipset is quite weak and the setting i
> left as default.
> 
> 
> Ming
> 


  reply	other threads:[~2005-07-05 13:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  2:15 raid0 low performance Ming Zhang
2005-07-01  2:28 ` Tyler
2005-07-01  2:57   ` John Madden
2005-07-01 12:41     ` Ming Zhang
2005-07-01 12:54       ` John Madden
2005-07-01 13:10         ` Ming Zhang
2005-07-01 12:32   ` Ming Zhang
2005-07-01 12:55 ` Guy
2005-07-01 13:17   ` Ming Zhang
2005-07-01 13:54     ` Ming Zhang
2005-07-05  0:13       ` Mark Hahn
2005-07-05  0:26         ` Ming Zhang
2005-07-05 13:19           ` Ming Zhang [this message]
2005-07-01 14:42     ` Ming Zhang

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=1120569587.5535.7.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=hahn@physics.mcmaster.ca \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).