From: Anssi Saari <as@sci.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: PROMBLEM: CD burning at 16x uses excessive CPU, although DMA is enabled
Date: Mon, 8 Apr 2002 19:17:21 +0300 [thread overview]
Message-ID: <20020408161721.GA18233@sci.fi> (raw)
In-Reply-To: <Pine.LNX.3.96.1020408104857.21476C-100000@gatekeeper.tmr.com> <1018278394.570.143.camel@psuedomode>
On Mon, Apr 08, 2002 at 11:06:28AM -0400, Ed Sweetman wrote:
> I'm not completely sure about burning audio, but linux doesn't read
> audio cds using DMA.
I didn't think this is relevant, except if I were trying to copy a CD on
the fly, but that's not the case. But I have now tried it, no change. In
fact, what I tried was this linux-2.4.19-pre5-jam2 patch collection
which includes that and low latency and O(1) scheduler patches, among
other things. Didn't seem to help, however.
next prev parent reply other threads:[~2002-04-08 16:15 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
2002-04-08 15:58 ` Bill Davidsen
2002-04-08 16:17 ` Anssi Saari [this message]
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=20020408161721.GA18233@sci.fi \
--to=as@sci.fi \
--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.