From: Georg Chini <georg.chini@triaton-webhosting.com>
To: linux-kernel@vger.kernel.org
Subject: pdflush uses all cpu-time with 2.6.7 and slow media
Date: Wed, 30 Jun 2004 11:55:46 +0200 [thread overview]
Message-ID: <40E28E22.8010606@triaton-webhosting.com> (raw)
Hello,
there seems to be a problem with pdflush and
slow media in 2.6.7. I'm using the packet-writing patch
maintained by Peter Osterlund to write to dvd+rw.
When I copy large files to the dvd, pdflush
starts using all cpu-time up to a point where
the system hangs completely. I found a posting here
with a similar problem concerning nfs and pdflush
(28.04.2004, Brent Cook). This thread mentions,
that the problem is not observable in 2.6.5.
So I tried 2.6.5 and everything works fine if
I set dirty_ratio in /proc/sys/vm to 15. With
the default value of 40 there are still some problems,
but it is way better than 2.6.7-bk12. BTW my machine
is a dual PIII.
Any idea what might cause the problem? Any more
information I should give?
As I'm not on the list, please CC to me in your replies.
Thanks in advance
Georg Chini
reply other threads:[~2004-06-30 9:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40E28E22.8010606@triaton-webhosting.com \
--to=georg.chini@triaton-webhosting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox