All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Rik van Riel <riel@redhat.com>
Cc: Paolo Ornati <ornati@fastwebnet.it>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.x: iowait problem while burning a CD
Date: Sat, 28 Feb 2004 17:39:30 -0500	[thread overview]
Message-ID: <404118A2.1060301@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402271915590.1747-100000@chimarrao.boston.redhat.com>

Rik van Riel wrote:
> On Fri, 27 Feb 2004, Paolo Ornati wrote:
> 
> 
>>trying to burn a CD "on the fly" I have noticed a strange thing. During the 
>>burning "iowait" remains enough low (~3%, MAX 10%) but, after a little 
>>time, it suddenly and quickly goes up to 80-90%: in this condition MKFS 
>>seems unable to fill the FIFO buffer as quickly as the CD-writer writes  
> 
> 
>>Any ideas?
> 
> 
> At that point, mkisofs is probably running into a bazillion
> small files, in subdirectories all over the place.
> 
> Because a disk seek + track read takes 10ms, it's simply not
> possible to read more than maybe 100 of these small files a
> second, so mkisofs can't keep up.

I certainly have seen this, although there is something odd in the 
process with large files as well. I sometimes see it in 2.4 as well, so 
it may be a characteristic of the application.

What to do about it (things to try, not requirements):

- use fs= to increase the size of the fifo a bit, remember to put "m"
   after the buffer size or it will be taken in bytes. This helps with
   the problem Rik describes
- be sure DMA is on the CD and the drive
- allow ints during io
- I'm told deadline schedular but haven't tried it
- get a new version of cdrecord, build with the 2.6 headers, use
   ATAPI:/dev/hdX for dev= instead of ide-scsi (this is probably not
   critical for data CD in 2.6.2 and later, ide-scsi seems to work)
- use burn-free
- drop the speed of the burn
- build the ISO image first, burn from that instead of a pipe
- use growisofs for DVD

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-02-28 22:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 17:02 2.6.x: iowait problem while burning a CD Paolo Ornati
2004-02-28  0:18 ` Rik van Riel
2004-02-28  9:14   ` Paolo Ornati
2004-02-28 14:52     ` Alex Bennee
2004-02-29  9:27       ` Paolo Ornati
2004-02-29 10:35         ` Mike Fedyk
2004-02-29 13:38           ` 2.6.x: iowait problem while burning a CD: SOLVED Paolo Ornati
2004-02-28 22:39   ` Bill Davidsen [this message]
2004-02-29  9:37     ` 2.6.x: iowait problem while burning a CD Paolo Ornati

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=404118A2.1060301@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ornati@fastwebnet.it \
    --cc=riel@redhat.com \
    /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.