From: "Martin J. Bligh" <mbligh@aracnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [Bug 530] New: dma not enabled for IDE hard drives
Date: Tue, 01 Apr 2003 12:59:46 -0800 [thread overview]
Message-ID: <137350000.1049230786@flay> (raw)
http://bugme.osdl.org/show_bug.cgi?id=530
Summary: dma not enabled for IDE hard drives
Kernel Version: 2.5.66
Status: NEW
Severity: normal
Owner: bugme-janitors@lists.osdl.org
Submitter: freelsjd@ornl.gov
Distribution: Debian/Sid
Hardware Environment: dual 2.4Ghz Xeon, SE7500CW2 MB, all Intel
Promise PDC20267 ATA-100 ide channels in
non-RAID mode
Software Environment: testing with hdparm 5.2-1 of Debian/Sid
Problem Description:
I have similar .config settings for both the 2.4.20 and the 2.5.66
kernels with the identical machine. Under 2.4.20, I do get dma enabled
and see good performance (Mb/s) from the hard disk I/O.
However, under the 2.5.66 kernel, dma is not enabled and the performance
of the hard drives is poor (~2-3 Mb/s under 2.4.20 versus ~30 Mb/s under
2.5.66). The "hdparm -I /dev/hda" command confirms that dma is not
enabled under 2.5.66, but is under 2.4.20.
Steps to reproduce:
reply other threads:[~2003-04-01 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=137350000.1049230786@flay \
--to=mbligh@aracnet.com \
--cc=linux-kernel@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