From: Yang Shi <yang.shi@linux.alibaba.com>
To: Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: YangShi <yang.shi@linux.alibaba.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [QUESTIONS] THP allocation in NUMA fault migration path
Date: Wed, 17 Apr 2019 21:15:41 -0700 [thread overview]
Message-ID: <aa34f38e-5e55-bdb2-133c-016b91245533@linux.alibaba.com> (raw)
Hi folks,
I noticed that there might be new THP allocation in NUMA fault migration
path (migrate_misplaced_transhuge_page()) even when THP is disabled (set
to "never"). When THP is set to "never", there should be not any new THP
allocation, but the migration path is kind of special. So I'm not quite
sure if this is the expected behavior or not?
And, it looks this allocation disregards defrag setting too, is this
expected behavior too?
Thanks,
Yang
next reply other threads:[~2019-04-18 4:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 4:15 Yang Shi [this message]
2019-04-18 6:32 ` Michal Hocko
2019-04-18 16:18 ` Yang Shi
2019-04-19 11:13 ` Mel Gorman
2019-04-19 16:28 ` Yang Shi
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=aa34f38e-5e55-bdb2-133c-016b91245533@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=aarcange@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.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