From: Con Kolivas <kernel@kolivas.org>
To: sboyce@blueyonder.co.uk
Cc: Nuno Monteiro <nuno@itsari.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.x Scheduler, preemption and responsiveness - puzzlement
Date: Mon, 12 Jul 2004 11:57:42 +1000 [thread overview]
Message-ID: <cone.1089597462.444239.28499.502@pc.kolivas.org> (raw)
In-Reply-To: <40F1E409.4040200@blueyonder.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Sid Boyce writes:
> Nuno Monteiro wrote:
>
>>
>> On 2004.07.11 23:55, Sid Boyce wrote:
>>
>>> I've been wondering why this is, I can't remember what the BIOS says
>>> about the hard drives, from memory it looked OK, I think it was set to
>>
>>
>> <snip snip>
>>
>>> PCI IDE nVidia Corporation nForce2 IDE (rev a2)
>>
>>
>> <snip snip>
>>
>>> # CONFIG_BLK_DEV_AMD74XX is not set
>>
>>
>> You don't have the driver for your IDE chipset compiled in. In the
>> "ATA/ ATAPI/MFM/RLL support" under "Device Drivers" menu select "AMD
>> and nVidia IDE support". Also, you can disable the "Generic PCI IDE
>> Chipset Support" and the "VIA82CXXX chipset support" you seem to have
>> enabled.
>>
>> Then you should be able to do DMA, and things will go a lot faster.
>>
>>
>> Hope this helps.
>>
>>
>>
>> Nuno
>
> Oops!, thanks. The previous motherboard used the VIA chipset, so that
> got missed when I changed over.
> Regards
> Sid.
DMA disabled is perhaps the most common reason for poor performance under
I/O loads. I think some cut down configurations that people have used from
their 2.4 installations have missed the appropriate IDE driver.
Cheers,
Con
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-12 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 22:08 Sid Boyce
2004-07-11 22:18 ` bert hubert
2004-07-11 22:55 ` Sid Boyce
2004-07-12 1:00 ` Alistair John Strachan
[not found] ` <20040712000137.GA3854@hobbes.itsari.int>
2004-07-12 1:06 ` Sid Boyce
2004-07-12 1:57 ` Con Kolivas [this message]
2004-07-12 9:19 ` Sid Boyce
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=cone.1089597462.444239.28499.502@pc.kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno@itsari.org \
--cc=sboyce@blueyonder.co.uk \
/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®