All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: CD and 2.6 - more data fewer answers
Date: Thu, 16 Dec 2004 15:06:16 -0500	[thread overview]
Message-ID: <cpsp7f$mve$1@gatekeeper.tmr.com> (raw)

I have a 2.6.7-rc1-mm1 test system with both IDE CD and USB CD-R. Both 
work fine as I normally use them, the CD-R is my primary backup device.

With all the discussion of DMA or not DMA, I decided to try some 
reads... I tried readcd using /dev/hdc and the user was 60%, sys 40%, no 
idle. Using ATAPI:0,0,0 I saw user 60%, sys 2% idle 38%. Then using the 
USB device I saw user 4%, sys 9%, idle 12%, wio 75%. The USB is much 
faster, so this looked right, and it appeared that on data reads DMA was 
being used. I have no idea where all the user CPU was going.

Then I turned on -c2scan to read 2352 byte sectors without the final 
error correct. With /dev/hdc I saw use 42%, sys 68%. Using ATAPI:0,0,0 I 
saw user 47%, sys 53%. And using the USB device the c2scan ended without 
reading any data.

The difference between /dev/hdc and ATAPI:0,0,0 is small, although 
consistent. The access by SCSI number failed with the USB drive, and 
/dev/scd0 resulted in "readcd: Invalid argument. Cannot get SCSI I/O 
buffer" when tried (yes, as root as well).

I make no claim that this sheds light on the question, just a sprinkle 
of data to provide flavor. I'll bring in an audio CD tomorrow and see 
what trying to rip that does, unless someone beats me to it.

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me

                 reply	other threads:[~2004-12-16 20:05 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='cpsp7f$mve$1@gatekeeper.tmr.com' \
    --to=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.