From: Yang Shi <yang.shi@linux.alibaba.com>
To: mgorman@techsingularity.net, Michal Hocko <mhocko@suse.com>,
Vlastimil Babka <vbabka@suse.cz>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [QUESTION] Is MPOL_F_MOF user visible?
Date: Fri, 8 Mar 2019 22:22:59 -0800 [thread overview]
Message-ID: <3f1f8f38-71fa-7a12-92cd-c3ad552518ff@linux.alibaba.com> (raw)
Hi folks,
When reading the mempolicy code, I got confused by MPOL_F_MOF flag. It
is defined in include/uapi/linux/mempolicy.h, so it looks visible to the
users. But, man page doesn't mention it at all. And, the code in
do_set_mempolicy() -> mpol_new() doesn't set it. It looks it is just set
by two places:
- NUMA default policy (preferred_node_policy)
- When MPOL_MF_LAZY is passed in. But, it is not configurable from
user since it is not valid MF
So, actually it can't be set by user with set_mempolicy()/mbind() APIs,
right? As long as the process' or vmas' policy is changed to non-default
one (i.e. MPOL_BIND), those processes or vmas are *not* eligible for
migrating with NUMA balancing anymore?
Thanks,
Yang
next reply other threads:[~2019-03-09 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 6:22 Yang Shi [this message]
2019-03-09 12:49 ` Mel Gorman
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=3f1f8f38-71fa-7a12-92cd-c3ad552518ff@linux.alibaba.com \
--to=yang.shi@linux.alibaba.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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