From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Rik van Riel <riel@redhat.com>, pavel@ucw.cz, linux-mm@kvack.org
Subject: Re: [PATCH] RSS limit enforcement for 2.6
Date: Fri, 06 Feb 2004 00:11:23 +1100 [thread overview]
Message-ID: <402240FB.7070801@cyberone.com.au> (raw)
In-Reply-To: <20040204231840.67cbb388.akpm@osdl.org>
Andrew Morton wrote:
Snip [RSS not effective]
>
>Note that there is still a problem in refill_inactive_zone():
>
> if (page_mapped(page)) {
>
> /*
> * Don't clear page referenced if we're not going
> * to use it.
> */
> if (!reclaim_mapped && !over_rsslimit) {
> list_add(&page->lru, &l_ignore);
> continue;
> }
>
> /*
> * probably it would be useful to transfer dirty bit
> * from pte to the @page here.
> */
> pte_chain_lock(page);
> if (page_mapped(page) &&
> page_referenced(page, &over_rsslimit) &&
> !over_rsslimit) {
> pte_chain_unlock(page);
> list_add(&page->lru, &l_active);
> continue;
> }
> pte_chain_unlock(page);
> }
>
>That first test of over_rsslimit is kinda bogus: we haven't run
>
Probably why it isn't reclaiming your mapped pages
>page_referenced() yet! But the recent change of moving that little chunk
>of code to before the page_referenced() check was correct.
>
>So to get this right, we may need to split the over-limit stuff apart from
>the page_referenced() processing.
>
>
This is one thing I was worried about with my change, and I
thought the same thing.
Have a function to check rss limit and could also move
referenced bits to the page's flags, then page_referenced could
just return TestClearPageReferenced.
--
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-02-05 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 17:51 [PATCH] RSS limit enforcement for 2.6 Rik van Riel
2004-01-27 17:51 ` Rik van Riel
2004-02-05 7:18 ` Andrew Morton
2004-02-05 13:11 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-15 23:21 Rik van Riel
2004-03-15 23:21 ` Rik van Riel
2004-03-16 6:08 ` Nick Piggin
2004-03-16 6:08 ` Nick Piggin
2004-03-18 22:04 ` Pavel Machek
2004-03-18 22:04 ` Pavel Machek
2004-03-25 14:44 ` Rik van Riel
2004-03-25 14:44 ` Rik van Riel
2004-03-25 22:23 ` Pavel Machek
2004-03-25 22:23 ` Pavel Machek
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=402240FB.7070801@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.