From: Stephan von Krawczynski <skraw@ithnet.com>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Memory Problem in 2.4.9 ?
Date: Wed, 22 Aug 2001 13:01:06 +0200 [thread overview]
Message-ID: <20010822130106.0c4d4bf1.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108220729380.280-100000@mikeg.weiden.de>
In-Reply-To: <20010822010649Z16145-32383+774@humbolt.nl.linux.org> <Pine.LNX.4.33.0108220729380.280-100000@mikeg.weiden.de>
On Wed, 22 Aug 2001 07:33:38 +0200 (CEST)
Mike Galbraith <mikeg@wen-online.de> wrote:
>> HAHAHA.. I was right, hurried whack with my little hammer _did_ bust
> it all to pieces :)
>
> This is also (very!) hurried and _lightly_ tested, but still cures my
> problem.. what do you think?
>
> -Mike
>
>
> --- linux-2.4.9/mm/vmscan.c.org Sun Aug 19 08:55:24 2001
> +++ linux-2.4.9/mm/vmscan.c Wed Aug 22 05:03:50 2001
> @@ -506,11 +506,17 @@
> }
[...]
> + if (++page->age > PAGE_AGE_START) {
I am not very experienced with the aging algorithm, but can this statement be false at all? I mean if I get that right page->age starts with PAGE_AGE_START, doesn't it?
> + del_page_from_inactive_dirty_list(page);
> + add_page_to_active_list(page);
> + page->age = PAGE_AGE_START;
> + continue;
> + }
> + list_del(page_lru);
> + list_add(page_lru, &inactive_dirty_list);
> continue;
> }
>
> @@ -927,7 +933,7 @@
> recalculate_vm_stats();
> }
>
> - if (!do_try_to_free_pages(GFP_KSWAPD, 1)) {
> + if (!do_try_to_free_pages(GFP_KSWAPD, 0)) {
> if (out_of_memory())
> oom_kill();
> continue;
> --- linux-2.4.9/mm/filemap.c.org Mon Aug 20 17:25:20 2001
> +++ linux-2.4.9/mm/filemap.c Wed Aug 22 05:07:35 2001
> @@ -980,12 +980,9 @@
> static inline void check_used_once (struct page *page)
> {
> if (!PageActive(page)) {
> - if (page->age)
> + if (++page->age > PAGE_AGE_START)
same here. Am I missing something?
> activate_page(page);
> - else {
> - page->age = PAGE_AGE_START;
> - ClearPageReferenced(page);
> - }
> + ClearPageReferenced(page);
> }
> }
>
>
>
next prev parent reply other threads:[~2001-08-22 11:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 13:46 Memory Problem in 2.4.9 ? Stephan von Krawczynski
2001-08-21 14:33 ` Daniel Phillips
[not found] ` <20010821194140.43b46b10.skraw@ithnet.com>
[not found] ` <20010821174918Z16114-32383+718@humbolt.nl.linux.org>
2001-08-21 18:17 ` Stephan von Krawczynski
2001-08-21 19:10 ` Daniel Phillips
2001-08-22 0:04 ` Stephan von Krawczynski
2001-08-22 0:43 ` Daniel Phillips
2001-08-22 0:48 ` Rik van Riel
2001-08-22 1:13 ` Daniel Phillips
2001-08-22 10:43 ` Stephan von Krawczynski
[not found] ` <Pine.LNX.4.33.0108220729380.280-100000@mikeg.weiden.de>
2001-08-22 11:01 ` Stephan von Krawczynski [this message]
2001-08-22 17:22 ` Mike Galbraith
2001-08-22 19:18 ` Stephan von Krawczynski
2001-08-23 4:57 ` Mike Galbraith
2001-08-22 11:52 ` Stephan von Krawczynski
-- strict thread matches above, loose matches on Subject: below --
2001-08-22 4:47 Tommy Wu
2001-08-22 19:32 ` Daniel Phillips
2001-08-22 19:05 ` Marcelo Tosatti
2001-08-23 1:11 ` Daniel Phillips
2001-08-23 0:10 ` Marcelo Tosatti
2001-08-23 2:29 ` Daniel Phillips
2001-08-23 1:19 ` Marcelo Tosatti
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=20010822130106.0c4d4bf1.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeg@wen-online.de \
/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