All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <Stephen.Clark@seclark.us>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "\"\\\"J.A.\\\" Magallón\"" <jamagallon@ono.com>,
	"Björn Steinbrink" <B.Steinbrink@gmx.de>,
	"Mark Lord" <lkml@rtr.ca>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	alan@lxorguk.ukuu.org.uk
Subject: Re: Abysmal PATA IDE performance
Date: Thu, 09 Nov 2006 09:39:53 -0500	[thread overview]
Message-ID: <45533DB9.4000405@seclark.us> (raw)
In-Reply-To: <1163062700.3138.467.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>>Probably your drives are renamed.
>>Before you had (wild guess, look at your boot log messages):
>>- ata bus -> hdc,hdd
>>- sata -> sda (if you really have any sata bus...)
>>
>>Now all hdX become sdX, and PATA is detected _before_ SATA, so you names
>>probaly became:
>>- ata via libata -> sda (HD), sr0 (CDROM)
>>- sata -> sdb.
>>    
>>
>
>on fedora this doesn't matter (due to mount-by-label)
>
>the bigger problem I suspect is that the sata modules aren't part of the
>initrd!
>
>you can force the issue by adding
>
>alias scsi_hostadapter1 ata_piix
>
>to the /etc/modprobe.conf file, and then recreating the initrd
>(see the mkinitrd tool, or just install the kernel rpm)
>
>
>
>
>  
>
Thanks all.

Arjan, using combined_mode=libata and making a new ramdisk increased my 
xfer rate from 1.xx mb/sec to 28.xx mb/sec.

I am curious as to why my friends dell inspiron 8200 with a 1.8ghz p4 
and the same drive using the same drive with FC6 and the standard ide 
module gets 44 to 45 mb/sec.

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)




  reply	other threads:[~2006-11-09 14:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 16:33 Abysmal PATA IDE performance Stephen Clark
2006-11-08 23:50 ` Mark Lord
2006-11-09  0:35   ` Stephen Clark
2006-11-09  2:07     ` Björn Steinbrink
2006-11-09  3:53       ` Stephen Clark
2006-11-09  8:40         ` J.A. Magallón
2006-11-09  8:58           ` Arjan van de Ven
2006-11-09 14:39             ` Stephen Clark [this message]
2006-11-09 14:54               ` Arjan van de Ven
2006-11-09 17:24                 ` Stephen Clark
2006-11-09 17:33                 ` Stephen Clark
2006-11-09 18:23                   ` Arjan van de Ven
2006-11-09 19:01                     ` Stephen Clark
2006-11-09 19:31                       ` Stephen Clark
2006-11-09 20:23                   ` Luca Tettamanti
2006-11-09 20:31                     ` Stephen Clark
2006-11-09 21:52                       ` Luca Tettamanti
2006-11-09 22:16                         ` Stephen Clark
2006-11-09 22:43                           ` Luca Tettamanti
2006-11-09 23:00                   ` Tejun Heo
2006-11-09 23:52                     ` Stephen Clark
2006-11-10  3:50                       ` Stephen Clark
2006-11-09 15:17               ` Alessandro Suardi
2006-11-09  7:52       ` Alan Cox

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=45533DB9.4000405@seclark.us \
    --to=stephen.clark@seclark.us \
    --cc=B.Steinbrink@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=jamagallon@ono.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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.