linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ethan Solomita <solo@google.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: meminfo returns inaccurate NR_FILE_PAGES
Date: Tue, 17 Apr 2007 21:06:29 -0700	[thread overview]
Message-ID: <46259945.8040504@google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704171655390.9381@schroedinger.engr.sgi.com>

Christoph Lameter wrote:
> On Tue, 17 Apr 2007, Ethan Solomita wrote:
>
>   
>>      Note that File Pages is 62040kB when MemUsed is only 4824kB. We do
>> __(dec|inc)_zone_page_state(page, NR_FILE_PAGES) whenever doing a
>> radix_tree_(delete|insert) from/to mapping->page_tree. Except we missed one:
>>     
>
> Right. Sigh. Does this fix it?
>
> Fix NR_FILE_PAGES and NR_ANON_PAGES accounting.
>   

    I don't think that there's a problem with NR_ANON_PAGES. 
unmap_and_move(), the caller of move_to_new_page(), calls try_to_unmap() 
which calls try_to_unmap_anon() which calls try_to_unmap_one() which 
calls page_remove_rmap() which in turn makes the call to 
__dec_zone_page_state. i.e. the rmap() code is handling NR_ANON_PAGES 
and NR_FILE_MAPPED pages correctly. It's just the NR_FILE_PAGES which 
are tied to the mapping's page tree, where the problem lies.
    -- Ethan

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-04-18  4:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 23:12 Ethan Solomita
2007-04-17 23:56 ` Christoph Lameter
2007-04-18  4:06   ` Ethan Solomita [this message]
2007-04-18  5:12     ` Christoph Lameter
2007-04-18  5:31       ` Ethan Solomita
2007-04-18  5:39         ` Christoph Lameter
2007-04-18  6:13           ` Ethan Solomita
2007-04-18 19:36             ` Christoph Lameter
2007-04-18 19:39               ` Ethan Solomita
2007-04-18 21:02                 ` Christoph Lameter
2007-04-18  4:49   ` Ethan Solomita

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=46259945.8040504@google.com \
    --to=solo@google.com \
    --cc=clameter@sgi.com \
    --cc=linux-mm@kvack.org \
    /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