From: Sascha Warner <prx@cinatas.ath.cx>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, WU Fengguang <wfg@mail.ustc.edu.cn>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 00/11] writeback bug fixes and simplifications
Date: Fri, 28 Dec 2007 05:27:38 +0100 [thread overview]
Message-ID: <47747B3A.5090304@cinatas.ath.cx> (raw)
In-Reply-To: <20071228150111.e9451632.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 27 Dec 2007 23:08:40 +0100 Sascha Warner <prx@cinatas.ath.cx> wrote:
>
>
>> 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.
>>
>>
>
> (some) cc's restored. Please, always do reply-to-all.
>
Hi Wu,
Your latest patch does fix the seen pdflush 100% issue :)
P.S.: Andrew, sorry my subject pretended I was subscribed to lkml, I am not.
I hoped for the script at lkml to pull the threads together because of
the subject.
Thank you,
Sascha Warner
next prev parent reply other threads:[~2007-12-29 4:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 22:08 [PATCH 00/11] writeback bug fixes and simplifications Sascha Warner
2007-12-28 23:01 ` Andrew Morton
2007-12-28 4:27 ` Sascha Warner [this message]
2007-12-29 6:50 ` Sam Ravnborg
[not found] ` <E1J8Ykz-0002zC-8Z@localhost>
2007-12-29 10:17 ` WU Fengguang
2007-12-29 14:56 ` Hans-Peter Jansen
[not found] ` <E1JCRh6-0002fD-F8@localhost.localdomain>
2008-01-09 3:33 ` WU Fengguang
[not found] ` <E1J8RZS-0005kk-TI@localhost>
2007-12-29 2:37 ` WU Fengguang
[not found] <20071228134119.112899193@mail.ustc.edu.cn>
2007-12-28 13:41 ` Fengguang Wu
-- strict thread matches above, loose matches on Subject: below --
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=47747B3A.5090304@cinatas.ath.cx \
--to=prx@cinatas.ath.cx \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wfg@mail.ustc.edu.cn \
/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