All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Luigi Semenzato <semenzato@chromium.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
	Douglas Anderson <dianders@google.com>,
	Dmitry Torokhov <dtor@google.com>,
	Sonny Rao <sonnyrao@google.com>
Subject: Re: [PATCH] mm: add counters for different page fault types
Date: Fri, 26 May 2017 13:06:22 +0900	[thread overview]
Message-ID: <20170526040622.GB17837@bbox> (raw)
In-Reply-To: <CAA25o9SH=LSeeRAfHfMK0JyPuDfzLMMOvyXz5RZJ5taa3hybhw@mail.gmail.com>

On Thu, May 25, 2017 at 08:54:09AM -0700, Luigi Semenzato wrote:
> Thank you Minchan, that's certainly simpler and I am annoyed that I
> didn't consider that :/
> 
> By a quick look, there are a few differences but maybe they don't matter?
> 
> 1. can a major (anon) fault result in a hit in the swap cache?  So
> pswpin will not get incremented and the fault will be counted as a
> file fault.

If it is swap cache hit, it's not a major fault which causes IO
so VM count it as minor fault, not major.

> 
> 2. pswpin also counts swapins from readahead --- which however I think
> we have turned off (at least I hope so, since readahead isn't useful
> with zram, in fact maybe zram should log a warning when readahead is
> greater than 0 because I think that's the default).

Yub, I expected you guys used zram with readahead off so it shouldn't
be a big problem.
About auto resetting readahead with zram, I agree with you.
But there are some reasons I postpone the work. No want to discuss
it in this thread/moment. ;)

> 
> Incidentally, I understand anon and file faults, but what's a shmem fault?

For me, it was out of my interest but if you want to count shmem fault,
maybe, we need to introdue new stat(e.g., PSWPIN_SHM) in shmem_swapin
but there are concrete reasons to justify in changelog. :)

Thanks!

--
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:[~2017-05-26  4:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 19:41 [PATCH] mm: add counters for different page fault types Luigi Semenzato
2017-05-25  0:19 ` Minchan Kim
2017-05-25 15:54   ` Luigi Semenzato
2017-05-26  4:06     ` Minchan Kim [this message]
2017-05-26 18:43       ` Luigi Semenzato
2017-05-29  8:15         ` Minchan Kim
2017-05-30 18:41           ` Luigi Semenzato
2017-05-31  1:31             ` Minchan Kim

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=20170526040622.GB17837@bbox \
    --to=minchan@kernel.org \
    --cc=dianders@google.com \
    --cc=dtor@google.com \
    --cc=linux-mm@kvack.org \
    --cc=semenzato@chromium.org \
    --cc=sonnyrao@google.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.