From: Stephen Clark <Stephen.Clark@seclark.us>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata and sata?
Date: Tue, 12 Dec 2006 12:30:09 -0500 [thread overview]
Message-ID: <457EE721.2090509@seclark.us> (raw)
In-Reply-To: <457ED87A.5@comcast.net>
John Richard Moser wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>A while back my distro moved to libata for sata_via. I was since
>confused; my disk seemed a lot slower, and it looked like DMA was off.
>I'm not sure how SATA works; is it even possible to enable/disable
>32-bit IO and DMA? Or are those just on?
>
>sata_via 11524 4
>libata 112660 3 ata_generic,pata_via,sata_via
>
>~$ sudo hdparm -d1 -c1 -u1 /dev/sda
>
>/dev/sda:
> setting 32-bit IO_support flag to 1
> HDIO_SET_32BIT failed: Invalid argument
> setting unmaskirq to 1 (on)
> HDIO_SET_UNMASKINTR failed: Inappropriate ioctl for device
> setting using_dma to 1 (on)
> HDIO_SET_DMA failed: Inappropriate ioctl for device
> IO_support = 0 (default 16-bit)
>
>I no longer have two kernels to test through; I can't tell if the speed
>is back or not. Nothing in dmesg tells me if SATA is using DMA or
>32-bit IO support though, so I don't know... lack of knowledge over here
>is killing me for troubleshooting this on my own.
>
>
>
<snip>
Hi John,
This happened to me with my ICH7 intel chipset which supports sata and ata - my drive was an ide and the performance was like 1.2mb/sec. Someone said boot with combined_mode=libata and it fixed the problem.
Now I get 44mb/sec.
HTH,
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2006-12-12 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 16:27 libata and sata? John Richard Moser
2006-12-12 17:30 ` Stephen Clark [this message]
2006-12-12 17:37 ` Alan
2006-12-19 0:41 ` John Richard Moser
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=457EE721.2090509@seclark.us \
--to=stephen.clark@seclark.us \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox