All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anssi Saari <as@sci.fi>
To: Markus Plail <plail@web.de>
Cc: Sergio Bruder <sergio@bruder.net>,
	Andre Hedrick <andre@linux-ide.org>,
	vojtech@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: CD burning at 12x uses excessive CPU, although DMA is enabled
Date: Sat, 31 Aug 2002 19:29:14 +0300	[thread overview]
Message-ID: <20020831162914.GA6310@sci.fi> (raw)
In-Reply-To: <873cswuvvi.fsf@plailis.homelinux.net>

On Fri, Aug 30, 2002 at 06:58:09PM +0200, Markus Plail wrote:
 
> If you write CDs in RAW modes, then there's the problem with the high
> loads. Examples:
> - cdrecord -raw96r/p (2448 bytes/sector)
> - cdrecord -raw16    (2368 bytes/sector)
> - cdrdao --driver generic-mmc-raw (2368 bytes/sector)
 
Yes, this is confirmed. I tried writing a data track with cdrecord
-raw96r mode and got the slowdown. So yes, it seems that "big" blocks,
2352 bytes and greater cause this problem while "small" blocks of 2048
bytes don't.


  parent reply	other threads:[~2002-08-31 16:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 20:06 PROMBLEM: CD burning at 16x uses excessive CPU, although DMA is enabled Roger Larsson
2002-04-09 20:27 ` Andre Hedrick
2002-04-10  9:10   ` Matthias Andree
2002-04-14 12:39   ` Anssi Saari
2002-08-30  4:33     ` PROBLEM: CD burning at 12x " Sergio Bruder
2002-08-30  4:48       ` Sergio Bruder
2002-08-30  6:14       ` Markus Plail
2002-08-30  6:51         ` Anssi Saari
2002-08-30  7:27           ` Markus Plail
2002-08-30 15:42             ` Anssi Saari
2002-08-30 16:58               ` Markus Plail
2002-08-30 21:22                 ` Sergio Bruder
2002-08-31 16:29                 ` Anssi Saari [this message]
2002-08-30  6:41       ` Andre Hedrick
2002-08-30 12:59         ` Henrique de Moraes Holschuh

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=20020831162914.GA6310@sci.fi \
    --to=as@sci.fi \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plail@web.de \
    --cc=sergio@bruder.net \
    --cc=vojtech@ucw.cz \
    /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.