linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-mm@kvack.org, hughd@google.com,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Zi Yan <ziy@nvidia.com>, John Hubbard <jhubbard@nvidia.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmstat: Add events for PMD based THP migration without split
Date: Wed, 3 Jun 2020 04:09:37 -0700	[thread overview]
Message-ID: <20200603110937.GP19604@bombadil.infradead.org> (raw)
In-Reply-To: <280304c7-882b-cb2f-55bf-87b2e2f28711@arm.com>

On Wed, Jun 03, 2020 at 10:28:41AM +0530, Anshuman Khandual wrote:
> On 06/03/2020 08:27 AM, Matthew Wilcox wrote:
> > On Wed, Jun 03, 2020 at 06:56:57AM +0530, Anshuman Khandual wrote:
> >> On 06/02/2020 08:31 PM, Matthew Wilcox wrote:
> >>> On Fri, May 22, 2020 at 09:04:04AM +0530, Anshuman Khandual wrote:
> >>>> This adds the following two new VM events which will help in validating PMD
> >>>> based THP migration without split. Statistics reported through these events
> >>>> will help in performance debugging.
> >>>>
> >>>> 1. THP_PMD_MIGRATION_SUCCESS
> >>>> 2. THP_PMD_MIGRATION_FAILURE
> >>>
> >>> There's nothing actually PMD specific about these events, is there?
> >>> If we have a THP of a non-PMD size, you'd want that reported through the
> >>> same statistic, wouldn't you?
> >>
> >> Yes, there is nothing PMD specific here and we would use the same statistics
> >> for non-PMD size THP migration (if any) as well. But is THP migration really
> >> supported for non-PMD sizes ? CONFIG_ARCH_ENABLE_THP_MIGRATION depends upon
> >> CONFIG_TRANSPARENT_HUGEPAGE without being specific or denying about possible
> >> PUD level support. Fair enough, will drop the PMD from the events and their
> >> functions.
> > 
> > I guess you haven't read my large pages patchset?
> 
> I believe you are referring this "[PATCH v5 00/39] Large pages in the page cache"
> (https://lkml.org/lkml/2020/5/28/1755). Unfortunately, I have not been following
> the series. But is there something else in particular that needs to be taken care
> of as well ?

I don't think so, but I haven't looked at the migration path at all.
I'm hoping it "just works", but experience with the rest of the mm has
taught me there's probably an assumption in there that THP => PMD that
will need to be fixed.  I'm not currently testing on a NUMA machine, and
I'm still debugging other paths.


      reply	other threads:[~2020-06-03 11:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  3:34 [PATCH] mm/vmstat: Add events for PMD based THP migration without split Anshuman Khandual
2020-06-01 16:57 ` Daniel Jordan
2020-06-02  3:20   ` John Hubbard
2020-06-02  4:20     ` Anshuman Khandual
2020-06-02  4:48       ` John Hubbard
2020-06-02  5:30         ` Anshuman Khandual
2020-06-02 14:52         ` Daniel Jordan
2020-06-03  4:36           ` Anshuman Khandual
2020-06-03 16:08             ` Daniel Jordan
2020-06-02 15:01 ` Matthew Wilcox
2020-06-03  1:26   ` Anshuman Khandual
2020-06-03  2:57     ` Matthew Wilcox
2020-06-03  4:58       ` Anshuman Khandual
2020-06-03 11:09         ` Matthew Wilcox [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=20200603110937.GP19604@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=hughd@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).