linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richardw.yang@linux.intel.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Wei Yang <richardw.yang@linux.intel.com>, linux-mm@kvack.org
Subject: Re: Why sometimes count vm event with page number, sometimes not?
Date: Tue, 5 Nov 2019 14:28:09 +0800	[thread overview]
Message-ID: <20191105062809.GA15848@richard> (raw)
In-Reply-To: <20191105033251.GB11823@bombadil.infradead.org>

On Mon, Nov 04, 2019 at 07:32:51PM -0800, Matthew Wilcox wrote:
>On Tue, Nov 05, 2019 at 10:26:44AM +0800, Wei Yang wrote:
>> Hi, All,
>> 
>> I am curious about the semantic of __count_vm_event[s].
>> 
>> For example, we count PGDEACTIVATE event in lru_deactivate_file_fn() and
>> lru_deactivate_fn(). One of them count with number of page, the other not.
>> 
>> Just curious about the exact value we want to count.
>
>I don't understand the question.  We deactivate one page
>in lru_deactivate_file_fn().  We deactivate several pages in
>shrink_active_list().  PGDEACTIVATE counts the number of pages which
>have been deactivated.
>
>Does that answer your question?

Not yet.

In function, lru_deactivate_fn(), __count_vm_events's second parameter is
hpage_nr_pages(page). This is the number in size of "normal" page. Per my
understanding, the page deactivated in lru_deactivate_file_fn() could be a
hpage too. But it just count the deactivation once instead of
hpage_nr_pages().

Or you want to say the page deactivated in lru_deactivate_file_fn() must be an
order 0 page?

-- 
Wei Yang
Help you, Help me


  reply	other threads:[~2019-11-05  6:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05  2:26 Wei Yang
2019-11-05  3:32 ` Matthew Wilcox
2019-11-05  6:28   ` Wei Yang [this message]
2019-11-05 15:40     ` Vlastimil Babka
2019-11-05 20:49       ` Hugh Dickins
2019-11-06  0:28         ` Wei Yang

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=20191105062809.GA15848@richard \
    --to=richardw.yang@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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