From: Louis Garcia <louisg00@bellsouth.net>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Problem with rmap-12c
Date: 08 Feb 2002 16:06:13 -0500 [thread overview]
Message-ID: <1013202380.1153.7.camel@tiger> (raw)
In-Reply-To: <Pine.LNX.4.33L.0202072006010.17850-100000@imladris.surriel.com>
In-Reply-To: <Pine.LNX.4.33L.0202072006010.17850-100000@imladris.surriel.com>
Ok, I've tried rmap-12d and the swaping is better but still worse then
12a. One thing I should say is I'm also using Andrews low latency patch.
Is you want vm stats let me know.
--Louis
On Thu, 2002-02-07 at 17:12, Rik van Riel wrote:
> On 7 Feb 2002, Louis Garcia wrote:
>
> > I tried rmap-12c and had lots of swap usage. I when back to 12a and
> > everything calmed down. Is their a known problem with 12c?
>
> Nope, but the RSS limit enforcing stuff is a possible
> suspect.
>
> It turns out I used a "struct pte_t" in over_rss_limit(),
> which turned into a compiler warning, for which I didn't
> spot the cause ;)
>
> A fix for the bug was sent by Roger Larsson, who spotted
> the fact that "pte_t" already has a "struct" inside it.
>
> Maybe page aging isn't working in rmap-12c because of this
> stupid mistake ... but it's a long shot. Maybe I should
> release rmap 12d tonight ? ;)
>
> regards,
>
> Rik
> --
> "Linux holds advantages over the single-vendor commercial OS"
> -- Microsoft's "Competing with Linux" document
>
> http://www.surriel.com/ http://distro.conectiva.com/
>
next prev parent reply other threads:[~2002-02-08 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 20:40 Problem with rmap-12c Louis Garcia
2002-02-07 22:12 ` Rik van Riel
2002-02-07 22:32 ` Shawn Starr
2002-02-07 23:30 ` Rik van Riel
2002-02-08 21:06 ` Louis Garcia [this message]
2002-02-08 21:30 ` Rik van Riel
2002-02-16 21:29 ` future of rmap VM Louis Garcia
2002-02-16 21:41 ` Rik van Riel
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=1013202380.1153.7.camel@tiger \
--to=louisg00@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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