From: Michal Hocko <mhocko@kernel.org>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: linux-mm@kvack.org, Zi Yan <zi.yan@sent.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] mm: migrate: vm event counter for hugepage migration
Date: Thu, 12 Apr 2018 08:18:59 +0200 [thread overview]
Message-ID: <20180412061859.GR23400@dhcp22.suse.cz> (raw)
In-Reply-To: <1523434167-19995-1-git-send-email-n-horiguchi@ah.jp.nec.com>
On Wed 11-04-18 17:09:25, Naoya Horiguchi wrote:
> Hi everyone,
>
> I wrote patches introducing separate vm event counters for hugepage migration
> (both for hugetlb and thp.)
> Hugepage migration is different from normal page migration in event frequency
> and/or how likely it succeeds, so maintaining statistics for them in mixed
> counters might not be helpful both for develors and users.
This is quite a lot of code to be added se we should better document
what it is intended for. Sure I understand your reasonaning about huge
pages are more likely to fail but is this really worth a separate
counter? Do you have an example of how this would be useful?
If we are there then what about different huge page sizes (for hugetlb)?
Do we need per-hstate stats?
In other words, is this really worth it?
> include/linux/vm_event_item.h | 7 +++
> mm/migrate.c | 103 +++++++++++++++++++++++++++++++++++-------
> mm/vmstat.c | 8 ++++
> 3 files changed, 102 insertions(+), 16 deletions(-)
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-12 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 8:09 Naoya Horiguchi
2018-04-11 8:09 ` [PATCH v1 1/2] mm: migrate: add vm event counters thp_migrate_(success|fail) Naoya Horiguchi
2018-04-11 19:16 ` kbuild test robot
2018-04-11 8:09 ` [PATCH v1 2/2] mm: migrate: add vm event counters hugetlb_migrate_(success|fail) Naoya Horiguchi
2018-04-12 6:18 ` Michal Hocko [this message]
2018-04-12 7:40 ` [PATCH v1 0/2] mm: migrate: vm event counter for hugepage migration Naoya Horiguchi
2018-04-12 7:47 ` Michal Hocko
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=20180412061859.GR23400@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vbabka@suse.cz \
--cc=zi.yan@sent.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