From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Anssi Saari <as@sci.fi>, linux-kernel@vger.kernel.org
Subject: Re: PROMBLEM: CD burning at 16x uses excessive CPU, although DMA is enabled
Date: 08 Apr 2002 11:06:28 -0400 [thread overview]
Message-ID: <1018278394.570.143.camel@psuedomode> (raw)
In-Reply-To: <Pine.LNX.3.96.1020408104857.21476C-100000@gatekeeper.tmr.com>
I'm not completely sure about burning audio, but linux doesn't read
audio cds using DMA. It just wont on ide devices. You can use a patch
that allows this from andrew morton. I dont write many audio cds so
I've never tested it's effect on writing a cd, only reading. I imagine
it's not safe to use dma on raw/audio cds. but go check it out
anyways.
On Mon, 2002-04-08 at 10:54, Bill Davidsen wrote:
> On Mon, 8 Apr 2002, Anssi Saari wrote:
>
> > [1.] One line summary of the problem:
> > CD burning at 16x uses excessive CPU, although DMA is enabled
>
> That's a hint things are not working as you expect...
>
> > [2.] Full description of the problem/report:
> > My system seems to use a lot of CPU time when writing CDs at 16x. The
> > system is unable to feed the burning software's buffer fast enough when
> > burning software (cdrecord 1.11a20, cdrdao 1.1.5) is run as normal user.
> > If run as root, system is almost unresponsive during the burn.
>
> With all the information you provided, you have totally not quatified
> how much CPU you find "excessive." I would not be surprised to see 10-15%
> of the CPU, virtually all in system time, as a normal burn of an ISO
> image. If the time is in user mode with other image types, it may well be
> that you are doing something which actually requires a lot of CPU (byte
> swapping or some such).
>
> Going from a disk to a CD using DMA on both should not take much
> *system* CPU, even if these are ATAPI (assuming they are not on the same
> cable).
>
> --
> bill davidsen <davidsen@tmr.com>
> CTO, TMR Associates, Inc
> Doing interesting things with little computers since 1979.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-04-08 15:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 12:26 PROMBLEM: CD burning at 16x uses excessive CPU, although DMA is enabled Anssi Saari
2002-04-08 14:54 ` Bill Davidsen
2002-04-08 15:06 ` Ed Sweetman [this message]
2002-04-08 15:58 ` Bill Davidsen
2002-04-08 16:17 ` Anssi Saari
2002-04-08 15:47 ` Anssi Saari
2002-04-08 17:35 ` Bill Davidsen
2002-04-08 19:06 ` Anssi Saari
2002-04-08 21:32 ` Roger Larsson
[not found] ` <Pine.LNX.4.33.0204081754010.10199-100000@coffee.psychology.mcmaster.ca>
2002-04-09 10:01 ` Anssi Saari
2002-04-09 13:33 ` Denis Vlasenko
2002-04-08 21:45 ` Mark Mielke
2002-04-09 0:10 ` Bill Davidsen
2002-04-09 8:32 ` Anssi Saari
2002-04-09 9:32 ` Wojtek Pilorz
2002-04-09 14:37 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2002-04-09 20:06 Roger Larsson
2002-04-09 20:27 ` Andre Hedrick
2002-04-10 9:10 ` Matthias Andree
2002-04-14 12:39 ` Anssi Saari
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=1018278394.570.143.camel@psuedomode \
--to=ed.sweetman@wmich.edu \
--cc=as@sci.fi \
--cc=davidsen@tmr.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.