mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: sboyce@blueyonder.co.uk
Cc: bert hubert <ahu@ds9a.nl>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.x Scheduler, preemption and responsiveness - puzzlement
Date: Mon, 12 Jul 2004 02:00:32 +0100	[thread overview]
Message-ID: <200407120200.32938.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <40F1C568.2070503@blueyonder.co.uk>

On Sunday 11 July 2004 23:55, Sid Boyce wrote:
[snip]
>
> 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
> AUTO, haven't tried LBA.
> # hdparm -d1 /dev/hda
>
> /dev/hda:
>  setting using_dma to 1 (on)
>  HDIO_SET_DMA failed: Operation not permitted
>  using_dma    =  0 (off)
> # hdparm -d1 /dev/hdc
>
> /dev/hdc:
>  setting using_dma to 1 (on)
>  HDIO_SET_DMA failed: Operation not permitted
>  using_dma    =  0 (off)
>

Your BIOS geometry settings are irrelevant. You've just forgotten to enable 
the correct busmaster DMA driver in your kernel. It looks as though this is 
an nForce 2 system, so you need to enable "Generic PCI bus-master DMA 
support", then further down "AMD and nVidia IDE support", in menuconfig. 
You'll then be able to set DMA on, and this will likely resolve the 
performance issue.

In .config, the relevant options are

CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_AMD74XX=y

Hope this helps!

-- 
Cheers,
Alistair.

personal:   alistair()devzero!co!uk
university: s0348365()sms!ed!ac!uk
student:    CS/AI Undergraduate
contact:    1F2 55 South Clerk Street,
            Edinburgh. EH8 9PP.

  reply	other threads:[~2004-07-12  1:00 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 [this message]
     [not found]     ` <20040712000137.GA3854@hobbes.itsari.int>
2004-07-12  1:06       ` Sid Boyce
2004-07-12  1:57         ` Con Kolivas
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=200407120200.32938.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.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®