From: Zlatko Calusic <zlatko@iskon.hr>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: [patch] mm-deactivate-fix-1
Date: 14 Jan 2001 16:48:55 +0100 [thread overview]
Message-ID: <87ae8uw2vs.fsf@atlas.iskon.hr> (raw)
In-Reply-To: Marcelo Tosatti's message of "Sun, 14 Jan 2001 10:57:30 -0200 (BRST)"
Marcelo Tosatti <marcelo@conectiva.com.br> writes:
> On 14 Jan 2001, Zlatko Calusic wrote:
>
> > I have noticed that in deactivate_page_nolock() function pages get
> > unconditionally moved from the active to the inact_dirty list. Even if
> > it is really easy with additional check to put them straight to the
> > inact_clean list if they're freeable. That keeps the list statistics
> > more accurate and in the end should result in a little bit less CPU
> > cycles burned (only one list transition, less locking). As a bonus,
> > the comment above the function is now correct. :)
> >
> > I have tested the patch thoroughly and couldn't find any problems with
> > it. It should be really safe as reclaim_page() already carefully
> > checks pages before freeing.
> >
> > Comments?
>
> We want to move all deactivated pages to the inactive dirty list to get
> FIFO behaviour while reclaiming them.
>
Ah, I see. Then your answer should be put above the function as a
comment. To help other souls digging around that code (like I'm
doing). :)
--
Zlatko
--
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/
prev parent reply other threads:[~2001-01-14 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-14 13:40 Zlatko Calusic
2001-01-14 12:57 ` Marcelo Tosatti
2001-01-14 15:48 ` Zlatko Calusic [this message]
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=87ae8uw2vs.fsf@atlas.iskon.hr \
--to=zlatko@iskon.hr \
--cc=linux-mm@kvack.org \
--cc=marcelo@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