From: Christian Schmid <webmaster@rapidforum.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Ben Greear <greearb@candelatech.com>,
Andrew Morton <akpm@osdl.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG: Slowdown on 3000 socket-machines tracked down
Date: Wed, 08 Jun 2005 04:26:33 +0200 [thread overview]
Message-ID: <42A65759.8050507@rapidforum.com> (raw)
In-Reply-To: <1110776689.5131.37.camel@npiggin-nld.site>
This makes me seriously to despair.... the bug/lock/freeze is still there in 2.6.12rc6 ...
I am seriously offering 1000 dollars to the one who fixes this. (No Joke. I NEED that fixed. If you
want me to give that money to some organization, tell me.)
Please come back to me if you need more details or tell me what I can do to help you track this
down. Review all postings before please. Its a vm-lock because even opening a /proc file needs
around 20-30 seconds...
Nick Piggin wrote:
> On Mon, 2005-03-14 at 05:53 +0100, Christian Schmid wrote:
>
>
>>>The other thing that worries me is your need for lower_zone_protection.
>>>I think this may be due to unbalanced highmem vs lowmem reclaim. It
>>>would be interesting to know if those patches I sent you improve this.
>>>They certainly improve reclaim balancing for me... but again I guess
>>>you'll be reluctant to do much experimentation :\
>>
>>I have tested your patch and unfortunately on 2.6.11 it didnt change anything :( I reported this
>>before, or do you mean something else? I am of course willing to test patches as I do not want to
>>stick with 2.6.10 forever.
>
>
> Well I hope that scheduler developments in progress will put future
> kernels at least on par with 2.6.10 again (and hopefully better).
>
> Yes you did report that my patch didn't help 2.6.11, but could those
> results have been influenced by the suboptimal HT scheduling? If so,
> I was interested in the results with HT turned off.
>
> Nick
>
>
> Find local movie times and trailers on Yahoo! Movies.
> http://au.movies.yahoo.com
>
>
next prev parent reply other threads:[~2005-06-08 2:28 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 17:10 BUG: Slowdown on 3000 socket-machines tracked down Christian Schmid
2005-03-07 0:45 ` Nick Piggin
2005-03-07 1:13 ` Ben Greear
2005-03-07 1:58 ` Christian Schmid
2005-03-07 2:57 ` Ben Greear
2005-03-07 5:14 ` Nick Piggin
2005-03-07 5:30 ` Willy Tarreau
2005-03-07 5:41 ` Nick Piggin
2005-03-07 5:42 ` Nick Piggin
2005-03-07 5:46 ` Willy Tarreau
2005-03-07 9:22 ` Ben Greear
2005-03-07 9:28 ` Nick Piggin
2005-03-08 6:30 ` Ben Greear
2005-03-08 16:41 ` Christian Schmid
2005-03-09 23:45 ` Ben Greear
2005-03-09 23:52 ` Christian Schmid
2005-03-10 0:18 ` Ben Greear
2005-03-10 0:24 ` Christian Schmid
2005-03-10 5:17 ` Andrew Morton
2005-03-10 9:00 ` Andi Kleen
2005-03-10 9:09 ` Andrew Morton
2005-03-10 9:12 ` Andi Kleen
2005-03-10 9:38 ` Andrew Morton
2005-03-10 19:03 ` Ben Greear
2005-03-10 18:51 ` Christian Schmid
2005-03-10 19:06 ` Christian Schmid
2005-03-11 15:29 ` Christian Schmid
2005-03-11 19:10 ` Ben Greear
2005-03-11 19:27 ` Christian Schmid
2005-03-14 4:40 ` Nick Piggin
2005-03-14 4:53 ` Christian Schmid
2005-03-14 5:04 ` Nick Piggin
2005-05-28 3:17 ` Christian Schmid
2005-06-08 2:26 ` Christian Schmid [this message]
2005-06-08 2:39 ` Nick Piggin
2005-06-08 2:44 ` Andrew Morton
2005-03-07 14:35 ` Christian Schmid
2005-03-07 23:37 ` Ben Greear
2005-03-07 2:07 ` Christian Schmid
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=42A65759.8050507@rapidforum.com \
--to=webmaster@rapidforum.com \
--cc=akpm@osdl.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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