public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: libata PATA patch update
Date: Tue, 09 May 2006 22:05:30 +0200	[thread overview]
Message-ID: <4460F60A.9080006@keyaccess.nl> (raw)
In-Reply-To: <1147177857.3172.70.camel@localhost.localdomain>

Alan Cox wrote:

>> am using slackware 10.2 (vanilla) "cdparanoia III release 9.8 (March 23, 
>> 2001)". A while ago someone on this list pointed to some patches for 
>> SG_IO use with cdparanoia but this made my machine highly unstable. 
>> Would you like me to retest with this new driver? If so, any specific 
>> version of cdparanoia?
> 
> I would be interested to know what happens if you try this, version
> doesn't matter.

Did so. Took vanilla cdparanoia-III-alpha9.8 from:

http://downloads.xiph.org/releases/cdparanoia/cdparanoia-III-alpha9.8.src.tgz

and then applied the labels and sgio patches from:

ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/os/i386/SRPMS/cdparanoia-alpha9.8-24.src.rpm

Unfortunately, the only difference with regular cdparanoia seems to be 
that info bit. Now it's just:

===
Checking /dev/cdrom for cdrom...

CDROM model sensed sensed: PLEXTOR CD-R   PREMIUM 1.06


Checking for SCSI emulation...
         Drive is ATAPI (using SCSI host adaptor emulation)

Checking for MMC style command set...
         Drive is MMC style
Verifying CDDA command set...
         Expected command set reads OK.
===

Nothing about the SG interface and no "Couldn't disable kernel command 
translation layer" bit therefore. It gives me the exact same times 
regular cdparanoia does; 15-25% user, 15-20% system. This might be 
expected; it seems not unlikely in fact that the SG_IO patch would only 
be expected to do something for usage through the IDE driver. Added Jens 
Axboe to the CC...

I rechecked that it does indeed make a difference for the IDE driver and 
it does. Almost immediate timeout/lockups again, as I reported once before:

http://lkml.org/lkml/2006/1/10/373

This does seem to be drive dependent -- I do not get this when ripping 
from my DVD-ROM drive (hdd, sr1). There is also no difference in times 
though between normal and patched cdparanoia on hdd, so as a summary of 
what this SG_IO patch is doing for me, "nothing useful" will do nicely.

Oh well; in any case, in the context of this pata test, no regressions!

Rene.


  reply	other threads:[~2006-05-09 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:06 libata PATA patch update Alan Cox
2006-05-08 16:54 ` Meelis Roos
2006-05-08 17:29 ` Kevin Radloff
2006-05-09 12:24   ` Alan Cox
2006-05-09 16:52     ` Kevin Radloff
2006-05-08 21:57 ` Matthieu CASTET
     [not found]   ` <1147178241.3172.74.camel@localhost.localdomain>
     [not found]     ` <4460D7D7.3070807@free.fr>
2006-05-10 21:24       ` matthieu castet
2006-05-08 23:48 ` Rene Herman
2006-05-09 12:30   ` Alan Cox
2006-05-09 20:05     ` Rene Herman [this message]
2006-05-23 23:26   ` Rene Herman
2006-05-24  0:11     ` Rene Herman

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=4460F60A.9080006@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --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