[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44E89BBA.9090809@gmail.com>
Date: Sun, 20 Aug 2006 13:28:26 -0400
From: Ryan Newberry <brnewber@...il.com>
To: Jan Engelhardt <jengelh@...ux01.gwdg.de>
CC: Mike Galbraith <efault@....de>, Ingo Molnar <mingo@...e.hu>,
Martin Bligh <mbligh@...igh.org>, linux-kernel@...r.kernel.org,
Andrew Morton <akpm@...l.org>
Subject: Re: [Bugme-new] [Bug 7027] New: CD Ripping speeds slow with 2.6.17
Jan Engelhardt wrote:
>>>> I'm skeptical. Is the source for this application available? I'd like
>>>> to see this problem.
>>>>
>>> (never mind. saw your other post, found source)
>>>
>> Hm. I can't get better than 1.4x rip speed out of it with a stock SuSE
>> 10.1 kernel (2.6.16). It's also using truckloads of cpu, whereas the CD
>> rippers that came with this distro use a percent or two.
>>
>
> What command did you use to rip?
>
>
>
> Jan Engelhardt
>
The ripper he's using is ripoff I assume (source code here:
http://prdownloads.sourceforge.net/ripoffc/ripoff-0.8.tar.gz?download
extraction functionality contained in src/RipOffExtractor.c) . It uses
libparanoia to do its job, like the cdparanoia command. On my system,
ripoff has high CPU usage with a 2.6.16 kernel as well, but it reports a
9.0x rate on average.
Could the fact that it has such high CPU usage be a possible reason I am
experiencing a slower ripping speed (1.2x) when the patch that was git
bisected is applied?
--
Ryan Newberry
http://ripoffc.sourceforge.net
"All mankind is divided into three classes: those that are immovable, those that are movable, and those that move." - Benjamin Franklin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists