All of lore.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13
Date: 17 Dec 2003 21:47:12 GMT	[thread overview]
Message-ID: <brqit0$7p7$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 200312171227.53913.gene.heskett@verizon.net

In article <200312171227.53913.gene.heskett@verizon.net>,
Gene Heskett  <gene.heskett@verizon.net> wrote:

| I'm using /dev/hdc for burning in the k3b configuration screens, 
| however that path may actually be defined.  I haven't quite "grok"ed 
| all the details, but it works, and works with <10% of the cpu 
| involved when burning.
| 
| To me, thats a roaring success :-)

I'm burning on a 2.4 kernel, using ide-scsi, and taking <1% CPU at 16x
burn, so you might check if your CD is set to use DMA, or if it's still
doing PIO. I use about 10% doing an audio burn, which does use PIO in
2.4 AFAIK.

You may be able to drop the CPU a good bit more.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  parent reply	other threads:[~2003-12-17 21:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17 15:09 no atapi cdrecord burning with 2.6.0-test11-bk10 / bk13 Thomas Voegtle
2003-12-17 15:20 ` Måns Rullgård
2003-12-17 16:08   ` Thomas Voegtle
2003-12-17 17:23   ` Martin Schlemmer
2003-12-17 16:19 ` Gene Heskett
2003-12-17 16:25   ` Thomas Voegtle
2003-12-17 16:41     ` Gene Heskett
2003-12-17 16:49       ` Jens Axboe
2003-12-17 17:27         ` Gene Heskett
2003-12-17 18:33           ` Jens Axboe
2003-12-17 21:47           ` bill davidsen [this message]
2003-12-17 16:30 ` bill davidsen
2003-12-17 16:48 ` Jens Axboe
2003-12-17 17:35   ` Thomas Voegtle
2003-12-17 18:11     ` Martin Schlemmer
2003-12-17 18:32     ` Jens Axboe

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='brqit0$7p7$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.