From: Pavel Machek <pavel@ucw.cz>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Rik van Riel <riel@redhat.com>, Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hugh Dickins <hugh@veritas.com>, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] RSS limit enforcement for 2.6
Date: Thu, 18 Mar 2004 23:04:32 +0100 [thread overview]
Message-ID: <20040318220432.GB1505@openzaurus.ucw.cz> (raw)
In-Reply-To: <405699C1.7010906@cyberone.com.au>
Hi!
> >Hugh Dickins found a bug in the 2.4-rmap RSS limit enforcing
> >code that may well explain why the previous port of the code
> >to 2.6 resulted in bad performance. The split active lists
> >in 2.4-rmap probably masked the largest damages, but in 2.6
> >it was very much visible.
> >
> >
>
> Hi Rik,
> What was the problem by the way?
When running lingvistics computation, machine got completely
unusable due to bad memory pressure. nice -n 19 was
useless. Memory limit should help.
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-03-18 22:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 23:21 Rik van Riel
2004-03-16 6:08 ` Nick Piggin
2004-03-18 22:04 ` Pavel Machek [this message]
2004-03-25 14:44 ` Rik van Riel
2004-03-25 22:23 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-01-27 17:51 Rik van Riel
2004-02-05 7:18 ` Andrew Morton
2004-02-05 13:11 ` Nick Piggin
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=20040318220432.GB1505@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
--cc=riel@redhat.com \
/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