Re: PS2 mouse going nuts during cdparanoia session.

[Jens Axboe <axboe@suse.de>]

On Wed, Jul 16 2003, Dave Jones wrote:
> On Wed, Jul 16, 2003 at 07:13:23PM +0200, Jens Axboe wrote:
> 
>  > > Ah right, I thought cdparanoia was still ripper de jour..
>  > > What's recommended these days?
>  > 
>  > It is, unfortunately it uses read/write on /dev/sg* directly so cannot
>  > be used with "new path" that is so much faster. It's been a while since
>  > I looked, I can check for a good cdda ripper that uses SG_IO tomorrow if
>  > you don't find one first.
> 
> Ok. I'll add a note about this to post-halloween-2.5 sometime too
> when www.codemonkey.org.uk reappears again.
> [sidenote: please folks, no more mails telling me about this site going away,
>  it'll be back real soon, it just had to be 'upgraded' to a raq2, which didn't
>  go quite as smoothly as planned.].

Isn't it always like that? :)

>  > I'm about to cave in and add block emulation of that part, too. It's a
>  > bit more code, though.
> 
> If it'll make apps like cdparanoia take the fast path without needing
> rewriting, then that sounds like a good idea, if only to stop the

That would be the point, yes. Whether it's worth it depends on how many
programs are using sg and not SG_IO that we care about.

> 'dancing mouse' problem, though this does seem to be running away
> from a bug rather than fixing it. The real question is why are the
> two interacting with each other like this..

The bug wants fixing too, of course. I'm betting it's time spent in
the ide interrupt handler that's killing it. So it can be made a little
better, but not a lot. non-dma ripping is always going to pull you down.
Even if you didn't have problems, you'd spend 80% of the cpu time
getting data off the drive leaving only 20% for encoding + the rest. If
you get the dma path going, it'll basically leave the system idle when
ripping (1-2% sys or something like that, in the noise almost).

-- 
Jens Axboe