Message-ID: <43ECB91E.6060109@astral.ro>
Date: Fri, 10 Feb 2006 18:02:38 +0200
From: Imre Gergely <imre.gergely@astral.ro>
Organization: Astral Telecom SA
User-Agent: Thunderbird 1.5 (X11/20051025)
MIME-Version: 1.0
To: Erik Mouw <erik@harddisk-recovery.com>
CC: linux-kernel@vger.kernel.org
Subject: Re: disabling libata
References: <43EC97C6.10607@astral.ro> <20060210141130.GE28676@harddisk-recovery.com> <43ECA035.5040302@astral.ro> <20060210142224.GF28676@harddisk-recovery.com>
In-Reply-To: <20060210142224.GF28676@harddisk-recovery.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1988
Lines: 42


Erik Mouw wrote:
> On Fri, Feb 10, 2006 at 04:16:21PM +0200, Imre Gergely wrote:
>> Erik Mouw wrote:
>>> On Fri, Feb 10, 2006 at 03:40:22PM +0200, Imre Gergely wrote:
>>>> i have a SATA hardisk, and am using FC4 with default kernel
>>>> (2.6.14-1.1644_FC4). i was wondering if it's possible to tell the kernel to use
>>>> the old ATA driver with SATA support instead of libata, for my harddisk to
>>>> appear as hdX, and not sdX.
>>> Why would you want to do that? SATA are driven by libata and the disks
>>> turn up as SCSI devices. There's no way around that (yet).
>> if i recompile the kernel, and leave out the libata part, and compile in
>> support for SATA, under ATA, the harddisks turn up as normal IDE devices (ie
>> hde, hdf, etc). i would like that without recompiling. if it's possible of course.
> 
> Yes, I know that's possible for some SATA adapters, but my question is
> why would you want to do that? The SATA support in the IDE subsystem is
> deprecated, you should really use libata.
> 
> 
> Erik
> 

maybe it's just me... but it looks like if as SCSI device the whole thing is
slower than with IDE. i haven't tested it yet, but as sda the system load is
very high, i did some tests with dd, and the CPU usage is always at 98-100%.
and when i'm copying something to another disk, the other programs barely move,
sometimes even the mouse gets stuck. i dunno where this is coming from. i
thought i try with the old driver.

maybe if you could give me some hints about how to test the whole thing, i
could post some results. i know that driver change isn't the answer, but i
still wanted to know if one can switch between the old and the libata driver
without recompiling (with some boot parameters to the kernel perhaps).


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/