All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Alex Bennee <kernel-hacker@bennee.com>
Cc: Rik van Riel <riel@redhat.com>,
	Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x: iowait problem while burning a CD
Date: Sun, 29 Feb 2004 10:27:34 +0100	[thread overview]
Message-ID: <200402291027.34655.ornati@fastwebnet.it> (raw)
In-Reply-To: <1077979936.2791.69.camel@cambridge.braddahead.com>

On Saturday 28 February 2004 15:52, Alex Bennee wrote:
> > >
> > > 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.
> >
> > No... mkfs is reading only ONE big file ( ~ 700 MB )!
> >
> > And my system shouldn't be so slow:
> >
> > CPU: AMD Duron 750
> > RAM: 128 MB PC100
> > HD: 7200 RPM udma 4
> > File System: ResiserFS
>
> Could this be related to your low(ish) physical memory and the need swap
> stuff in and out? Maybe you could look at the vmstat output as you run
> the two cases?

No... swap is never touched !

But I think to have found where the problem is:

if I only create an ISO image of 672.4 MB I must wait more then 5 minutes... 
this means about 2.2 MB/s !

If I write a CD at 16x (~2400 KB/s) how can the image creation process be to 
the step with the writing one?

OK, if I create an ISO image I must (read from)/(write to) the disk, while 
burning on-the-fly requires only "read from disk".... But what happens if I 
write at 24x / 32x / 40x ???

Is 2,2 MB/s one acceptable speed?

My HD:

/dev/hda:

 multcount    = 16 (on)
 IO_support   =  1 (32-bit)
 unmaskirq    =  1 (on)
 using_dma    =  1 (on)
 keepsettings =  0 (off)
 readonly     =  0 (off)
 readahead    = 256 (on)
 geometry     = 38792/16/63, sectors = 39102336, start = 0

/dev/hda:

 Model=WDC WD200BB-53AUA1, FwRev=18.20D18, SerialNo=WD-WMA6Y1501425
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=57600, SectSize=600, ECCbytes=40
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39102336
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 *udma4 udma5 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: device does not report version:  1 2 3 4 5


FILE SYSTEM: ReiserFS


I have also noticed that raising the writing speed (24x/32x) I have the same 
problems with the buffer also having created the ISO image!

Bye

-- 
	Paolo Ornati
	Linux v2.6.3


  reply	other threads:[~2004-02-29  9:27 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 [this message]
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   ` 2.6.x: iowait problem while burning a CD Bill Davidsen
2004-02-29  9:37     ` 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=200402291027.34655.ornati@fastwebnet.it \
    --to=ornati@fastwebnet.it \
    --cc=kernel-hacker@bennee.com \
    --cc=linux-kernel@vger.kernel.org \
    --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.