From: Sascha Warner <prx@cinatas.ath.cx>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/11] writeback bug fixes and simplifications
Date: Thu, 27 Dec 2007 23:08:40 +0100 [thread overview]
Message-ID: <47742268.8040302@cinatas.ath.cx> (raw)
Hi,
I applied your patches to 2.6.24-rc6-mm1, but now I am faced with one
pdflush often using 100% CPU for a long time. There seem to be some rare
pauses from its 100% usage, however.
On ~23 minutes uptime i have ~19 minutes pdflush runtime.
This is on E6600, x86_64, 2 Gig RAM, SATA HDD, running on gentoo ~x64_64
Let me know if you need more info.
Prost,
Sascha Warner
next reply other threads:[~2007-12-28 22:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 22:08 Sascha Warner [this message]
2007-12-28 23:01 ` [PATCH 00/11] writeback bug fixes and simplifications Andrew Morton
2007-12-28 4:27 ` Sascha Warner
2007-12-29 6:50 ` Sam Ravnborg
2007-12-29 10:17 ` WU Fengguang
2007-12-29 10:17 ` WU Fengguang
2007-12-29 14:56 ` Hans-Peter Jansen
2008-01-09 3:33 ` WU Fengguang
2008-01-09 3:33 ` WU Fengguang
2007-12-29 2:37 ` WU Fengguang
2007-12-29 2:37 ` WU Fengguang
-- strict thread matches above, loose matches on Subject: below --
2007-12-28 13:41 Fengguang Wu
2007-12-28 13:41 ` Fengguang Wu
2008-01-11 19:05 Martin Knoblauch
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=47742268.8040302@cinatas.ath.cx \
--to=prx@cinatas.ath.cx \
--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 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.