mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ryan Newberry <brnewber@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Ingo Molnar <mingo@elte.hu>, Martin Bligh <mbligh@mbligh.org>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [Bugme-new] [Bug 7027] New: CD Ripping speeds slow with 2.6.17
Date: Sun, 20 Aug 2006 22:56:06 +0000	[thread overview]
Message-ID: <1156114566.5808.44.camel@Homer.simpson.net> (raw)
In-Reply-To: <44E89BBA.9090809@gmail.com>

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


  reply	other threads:[~2006-08-20 20:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608191800.k7JI0ML0015395@fire-2.osdl.org>
2006-08-19 18:14 ` Andrew Morton
2006-08-19 18:53   ` mbligh
2006-08-20  8:27   ` Mike Galbraith
2006-08-20 10:03     ` Mike Galbraith
2006-08-20 11:11       ` Mike Galbraith
2006-08-20 13:48         ` Jan Engelhardt
2006-08-20 17:28           ` Ryan Newberry
2006-08-20 22:56             ` Mike Galbraith [this message]
2006-08-22 12:02             ` Jan Engelhardt

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=1156114566.5808.44.camel@Homer.simpson.net \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=brnewber@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@mbligh.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome