mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roger Larsson <roger.larsson@skelleftea.mail.telia.com>
To: Andrea Arcangeli <andrea@suse.de>,
	Moritz Franosch <jfranosc@physik.tu-muenchen.de>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: IO performance problems in 2.4.19-pre5 when writing to DVD-RAM/ZIP/MO
Date: Tue, 16 Apr 2002 21:14:09 +0200	[thread overview]
Message-ID: <200204162114.09589.roger.larsson@skelleftea.mail.telia.com> (raw)
In-Reply-To: <rxxadshj1rh.fsf@synapse.t30.physik.tu-muenchen.de> <20020416165358.E29747@dualathlon.random>

On Tuesday 16 April 2002 16.53, Andrea Arcangeli wrote:
> The reason hd is faster is because new algorithm is much better than the
> previous mainline code. Now the reason the DVDRAM hangs the machine
> more, that's probably because more ram can be marked dirty with those
> new changes (beneficial for some workload, but it stalls much more the
> fast hd, if there's one very slow blkdev in the system). You can try
> decrasing the percent of vm dirty in the system with:
>
>
>         echo 2 500 0 0 500 3000 3 1 0 >/proc/sys/vm/bdflush
>
>
> hope this helps,
>
>
> Right fix is different but not suitable for 2.4.
>
>
> Andrea

In an other recent thread "PROMBLEM: CD burning at 16x uses excessive CPU, 
although DMA is enabled" it was found out that writing to CD-R did not use 
DMA. This resulted in lots of wasted CPU cycles.

>From a main by Anssi Saari
> cdrdao simulate -n --speed 8 foo.cue  2.62s user 3.37s system 1% cpu 6:41
> cdrdao simulate -n --speed 12 foo.cue  2.78s user 29.91s system 12% cpu 4:31
> cdrdao simulate -n --speed 16 foo.cue  2.67s user 128.8s system 52% cpu 4:11

> But even though 50% is quite high, CPU load is not the problem as such,
> the problem is getting data to the writer fast enough. And it's not
> happening. Even a single audio track that is completely cached so that
> there is no HD access has problems. It's like somehow accessing the CD
> writer hogs the system for such long periods that there is insufficient
> time to fill the writing program's buffer.

Might this be part of the problem in this case too? Moritz please time your 
commands and use vmstat too... (time spent in interrupt while running the
idle process - does not always show up)


/RogerL

-- 
Roger Larsson
Skellefteå
Sweden



  parent reply	other threads:[~2002-04-16 19:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <rxxadshj1rh.fsf@synapse.t30.physik.tu-muenchen.de>
2002-04-16 14:53 ` Andrea Arcangeli
2002-04-16 15:39   ` Rik van Riel
2002-04-16 16:25     ` Andrea Arcangeli
2002-04-17 15:35     ` Moritz Franosch
2002-04-16 16:09   ` Alan Cox
2002-04-16 16:40     ` Rik van Riel
2002-04-16 16:41     ` Andrea Arcangeli
2002-04-17 15:47     ` Moritz Franosch
2002-04-16 19:14   ` Roger Larsson [this message]
2002-04-17 19:12     ` Moritz Franosch
2002-04-17 15:26   ` Moritz Franosch
2002-04-17 16:34     ` Andreas Dilger
2002-04-17 17:32     ` Andrea Arcangeli

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=200204162114.09589.roger.larsson@skelleftea.mail.telia.com \
    --to=roger.larsson@skelleftea.mail.telia.com \
    --cc=andrea@suse.de \
    --cc=jfranosc@physik.tu-muenchen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®