From: Rik van Riel <riel@conectiva.com.br>
To: Rajagopal Ananthanarayanan <ananth@sgi.com>
Cc: riel@conectiva.com, linux-mm@kvack.org
Subject: Re: lru_cache_add() -> deactivate_page_nolock()?
Date: Fri, 29 Sep 2000 11:34:10 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0009291133190.23266-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <39D3F272.BC026A47@sgi.com>
On Thu, 28 Sep 2000, Rajagopal Ananthanarayanan wrote:
> Two cases here, depending on what happened in __alloc_pages():
>
> 1. page->age will be PAGE_AGE_START if page was previously
> freed (__free_pages_ok() sets the age)
>
> 2. page->age will be zero if page was obtained through
> a reclaim_page().
>
> I can't believe this was a design choice. Simply
> code like this is missing at the bottom of reclaim_page():
>
> ---------
> struct page * reclaim_page(zone_t * zone)
> {
> [ ... ]
> if (page)
> page->age = PAGE_START_AGE;
> return page;
> }
> ----------
>
> This will avoid nasty deactivation immediately on
> entering the page into the cache.
>
> ... btw, I have tried the above fix, and it does
> improve dbench performance in cases where few
> clients (1-2) are used on my 64MB system.
>
> Rik, what do you think?
You're absolutely right.
This is a bug which should be fixed.
regards,
Rik
--
"What you're running that piece of shit Gnome?!?!"
-- Miguel de Icaza, UKUUG 2000
http://www.conectiva.com/ http://www.surriel.com/
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-29 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8r0dot$13eak9$1@fido.engr.sgi.com>
2000-09-29 1:37 ` Rajagopal Ananthanarayanan
2000-09-29 14:34 ` Rik van Riel [this message]
2000-09-28 21:36 Rajagopal Ananthanarayanan
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=Pine.LNX.4.21.0009291133190.23266-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=ananth@sgi.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.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