public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Kyle <kyle@southa.com>
Cc: Bas Mevissen <ml@basmevissen.nl>, linux-kernel@vger.kernel.org
Subject: Re: ICH5 with 2.6.1 very slow
Date: Thu, 12 Feb 2004 08:41:10 +0000	[thread overview]
Message-ID: <20040212084110.GB20898@mail.shareable.org> (raw)
In-Reply-To: <004501c3f0ae$ecdd2ec0$b8560a3d@kyle>

Kyle wrote:
> Today I tried with compile the kernel 2.6.1 with:
> 
> IGNORE word93 Validation BITS (IDEDMA_IVB) = y
> 
> The result looks a bit better, got 30MB/s at /dev/hda and 37MB/s at /dev/hdc
> (38MB/s and 55MB/s at kernel 2.4.20)

Aha...

Have a look at the thread called "[RFC] IDE 80-core cable detect -
chipset-specific code to over-ride eighty_ninty_three()".

It specifically deals with ICH5 and is probably the same problem as
you're seeing.

-- Jamie

  reply	other threads:[~2004-02-12  8:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 16:40 ICH5 with 2.6.1 very slow Kyle
2004-02-05 17:23 ` Bas Mevissen
2004-02-05 17:27   ` Kyle
2004-02-05 17:30     ` Bas Mevissen
2004-02-05 17:33       ` Kyle
2004-02-06 10:10         ` Bas Mevissen
2004-02-06 21:32           ` Kyle
2004-02-09  8:32             ` Bas Mevissen
2004-02-09  8:56               ` Kyle Wong
2004-02-11 14:54               ` Kyle
2004-02-12  8:41                 ` Jamie Lokier [this message]
2004-02-12 14:08                   ` Kyle
2004-02-12 14:32                   ` Bas Mevissen
2004-02-12 19:28                     ` Jeff Garzik
2004-02-13  3:40                       ` Kyle
  -- strict thread matches above, loose matches on Subject: below --
2004-02-13 10:50 Daniel Blueman
2004-02-15 18:48 Kyle
2004-02-15 19:19 ` Bartlomiej Zolnierkiewicz
2004-02-15 19:23   ` Martin Schlemmer
2004-02-16 13:58     ` Kyle

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=20040212084110.GB20898@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=kyle@southa.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ml@basmevissen.nl \
    /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