linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: TJ <systemloc@earthlink.net>
To: linux-raid@vger.kernel.org
Subject: Re: Looking for the cause of poor I/O performance
Date: Fri, 3 Dec 2004 02:12:38 -0500	[thread overview]
Message-ID: <200412030212.38288.systemloc@earthlink.net> (raw)
In-Reply-To: <200412021138.17311.systemloc@earthlink.net>

Here's some info on the VIA chipset problem..

Here's the article that really cracked the VIA chipset problem. It seems there 
are problems with the default timings and latency settings:
http://www.tecchannel.de/hardware/817/8.html

This guy, independant of VIA, came up with some chipset register tweaks to 
improve performance of the PCI bus for the broken VIAs.
http://www.georgebreese.com/net/software/
http://www.georgebreese.com/net/software/readmes/vlatency_v020b21_readme.HTM
http://adsl.cutw.net/dlink-dsl200-via.html


The linux kernel sources indicate a problem with VIA chipsets too, but the 
author doesn't have it fixed to his satisfaction, obviously.

From linux-2.6.7/drivers/pci/quirks.c:

/*  The VIA VP2/VP3/MVP3 seem to have some 'features'. There may be a 
workaround
    but VIA don't answer queries. If you happen to have good contacts at VIA
    ask them for me please -- Alan

    This appears to be BIOS not version dependent. So presumably there is a
    chipset level fix */


I'm wondering if I could get the tweaks that George Breese has made and 
implement them in linux. If I could, how would I benchmark to check for 
improvement? Bonnie? hdparm -tT? Some PCI benchmark?

TJ Harrell

  parent reply	other threads:[~2004-12-03  7:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 16:38 Looking for the cause of poor I/O performance TJ
2004-12-03  0:49 ` Mark Hahn
2004-12-03  3:54   ` Guy
2004-12-03  6:33     ` TJ
2004-12-03  7:38       ` Guy
2004-12-04 15:23     ` TJ
2004-12-04 17:59       ` Guy
2004-12-04 23:51         ` Mark Hahn
2004-12-05  1:00           ` Steven Ihde
2004-12-06 17:48             ` Steven Ihde
2004-12-06 19:29               ` Guy
2004-12-06 21:10                 ` David Greaves
2004-12-06 23:02                   ` Guy
2004-12-08  9:24                     ` David Greaves
2004-12-08 18:31                       ` Guy
2004-12-08 22:00                         ` Steven Ihde
2004-12-08 22:25                           ` Guy
2004-12-08 22:41                             ` Guy
2004-12-09  1:40                               ` Steven Ihde
2004-12-12  8:56                               ` Looking for the cause of poor I/O performance - a test script David Greaves
2004-12-28  0:13                                 ` Steven Ihde
2004-12-06 21:16                 ` Looking for the cause of poor I/O performance Steven Ihde
2004-12-06 21:42                   ` documentation of /sys/vm/max-readahead Morten Sylvest Olsen
2004-12-05  2:16           ` Looking for the cause of poor I/O performance Guy
2004-12-05 15:14             ` TJ
2004-12-06 21:39               ` Mark Hahn
2004-12-05 15:17           ` TJ
2004-12-06 21:34             ` Mark Hahn
2004-12-06 23:06               ` Guy
2004-12-03  6:51   ` TJ
2004-12-03 20:03   ` TJ
2004-12-04 22:59     ` Mark Hahn
2004-12-03  7:12 ` TJ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-03 11:30 TJ
2004-12-03 11:46 ` Erik Mouw
2004-12-03 15:09   ` TJ
2004-12-03 16:25     ` Erik Mouw
2004-12-03 16:32   ` David Greaves
2004-12-03 16:50     ` Guy

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=200412030212.38288.systemloc@earthlink.net \
    --to=systemloc@earthlink.net \
    --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).