linux-kernel - Re: [Bugme-new] [Bug 7027] New: CD Ripping speeds slow with 2.6.17

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 20 Aug 2006 22:56:06 +0000
From:	Mike Galbraith <efault@....de>
To:	Ryan Newberry <brnewber@...il.com>
Cc:	Jan Engelhardt <jengelh@...ux01.gwdg.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

On Sun, 2006-08-20 at 13:28 -0400, Ryan Newberry wrote:
> 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.

Watching the .16 kernel, it boosts to interactive status frequently, but
even with this mega-boost, it uses so much cpu that it repeatedly falls
into the expire (unbounded latency) category.

At this point, I think this app has problems.

> 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?

Short answer, with a lot of interpolation, yes.

	-Mike

-
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/