From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10 and high cpu usage on reading out CDs with cdrtools and -clone
Date: Fri, 07 Jan 2005 17:33:39 +0100 [thread overview]
Message-ID: <41DEB9E3.8060206@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 659 bytes --]
I am not sure whether it is a cdrtools or kernel problem. I just noticed
using this command:
/usr/bin/readcd -v dev=/dev/hdc f=image.img -clone retries=128
leads to 100% CPU usage (depending on read speed). Writing this image is
no problem though (in high-speed). DMA is activated and using cdrdao CPU
usage stays low on reading the image. Leaving out the option -clone
option CPU usage stays low, as well. So is reading subchannels a
problem? But AFAIk cdrdao is configured to read subchannels, as well,
but doesn't show this problem (but I don't know whether it only reads
audio subchannels, though).
Anybody else making this observation?
bye,
Prakash
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-01-07 16:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=41DEB9E3.8060206@gmx.de \
--to=prakashkc@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome