From: Chris Mason <mason@suse.com>
To: Spam <spam@tnonline.net>
Cc: reiserfs-list@namesys.com
Subject: Re: CPU usage problem with custom 2.6.7 kernel
Date: Mon, 16 Aug 2004 09:48:56 -0400 [thread overview]
Message-ID: <1092664136.12138.64.camel@watt.suse.com> (raw)
In-Reply-To: <1677610534.20040814123650@tnonline.net>
On Sat, 2004-08-14 at 06:36, Spam wrote:
> >
> You need to enable DMA and 32bit I/O!
> Use: hdparm -d1c3 /dev/hda
>
DMA is the major problem there. hdparm -d1 /dev/hda should be enough to
fix the performance problems. The rest of the hints given in the
message are just tuning on top of dma, I'd suggest reading the hdparm
manpage carefully before changing any of them.
-chris
prev parent reply other threads:[~2004-08-16 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-14 10:24 CPU usage problem with custom 2.6.7 kernel Patrick Coleman
2004-08-14 10:36 ` Spam
2004-08-16 13:48 ` Chris Mason [this message]
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=1092664136.12138.64.camel@watt.suse.com \
--to=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=spam@tnonline.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.