linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Linda Walsh <lkml@tlinx.org>, LKML <linux-kernel@vger.kernel.org>,
	ide <linux-ide@vger.kernel.org>
Subject: Re: SATA kernel-buffered read VERY slow (not raid, Promise TX300 card); 2.6.23.1(vanilla)
Date: Tue, 01 Jan 2008 11:06:04 -0500	[thread overview]
Message-ID: <477A64EC.40401@rtr.ca> (raw)
In-Reply-To: <47798A28.2010301@shaw.ca>


>>>> I wanted to use the newer pata support in the SATA lib, but
>>>> got frustrated "real fast" by the lack of disk-parameter support
>>>> in the new pata library (hdparm is mostly broken; and the SCSI
>>>> utils aren't really intended for ATA(or SATA?) disks using the
>>>> SCSI interface.
...

Most hdparm flags work perfectly fine with libata,
unless perhaps you're using Fedora, which for some odd
reason was using a 2+ year old copy of hdparm until
very very recently.

As others noted, the only things not working are things that
libata itself chooses not to allow from userspace because libata
has better low-level drivers that can set those things automatically
in a more reliable fashion than we ever could with drivers/ide:
  DMA, 32-bit I/O, PIO/DMA xfer rates, hotplug stuff.

The rest, including acoustic and power-saving parameters,
work just fine with libata.

Cheers

  reply	other threads:[~2008-01-01 16:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.6TIOCGhBpW0r4XW9rqR+Ad8P+Js@ifi.uio.no>
     [not found] ` <4777E08C.4000603@shaw.ca>
     [not found]   ` <4779870E.5070507@tlinx.org>
2008-01-01  0:32     ` SATA kernel-buffered read VERY slow (not raid, Promise TX300 card); 2.6.23.1(vanilla) Robert Hancock
2008-01-01 16:06       ` Mark Lord [this message]
     [not found]     ` <pan.2008.01.01.01.45.23.430875@wizards.de>
2008-01-02 18:40       ` Linda Walsh
2008-01-03 17:54         ` Holger Hoffstaette
     [not found]     ` <20080101015812.59e9ebf0@the-village.bc.nu>
2008-01-02 20:09       ` Linda Walsh
2008-01-03  0:25         ` Robert Hancock
2008-01-03  4:25           ` Linda Walsh
2008-01-03  8:37             ` Mikael Pettersson
2008-01-04  2:37               ` Re:Believed resolved: SATA kern-buffRd read slow: based on promise driver bug Linda Walsh
2008-01-04  2:49                 ` Believed " Robert Hancock
2008-01-04 11:23                 ` Mikael Pettersson
2008-01-06 20:21                   ` Believed " Linda Walsh
2008-01-09  2:30                     ` Tejun Heo
     [not found] <fa.o9uy6Qaq3PtHs2Z9lAKGUKvD85I@ifi.uio.no>
     [not found] ` <fa.1kDEq2SPE3FqpM5Mfw9CVGbvVdY@ifi.uio.no>
     [not found]   ` <fa.hIZ5+XhGRugySB/HuLxr5qd6gAY@ifi.uio.no>
     [not found]     ` <fa.iefWPg3R6g5Pnm/ktSCK9XWVFVw@ifi.uio.no>
     [not found]       ` <fa.FhpaleM/osLTMJ85/PuxjxyJeGI@ifi.uio.no>
     [not found]         ` <fa.MP5rgMp4TS2+Cfemd/uFOQOuquQ@ifi.uio.no>
2008-01-04  2:35           ` SATA kernel-buffered read VERY slow (not raid, Promise TX300 card); 2.6.23.1(vanilla) Robert Hancock
2008-01-04  2:43             ` Linda Walsh
2008-01-04  2:56               ` Robert Hancock
2008-01-06 20:25                 ` Linda Walsh
2008-01-06 21:30                   ` Mehmet Kemal EROL
2008-01-06 22:43                   ` 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=477A64EC.40401@rtr.ca \
    --to=liml@rtr.ca \
    --cc=hancockr@shaw.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.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;
as well as URLs for NNTP newsgroup(s).