From: Michal Hocko <mhocko@suse.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Ben Widawsky <ben.widawsky@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Feng Tang <feng.tang@intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
Mike Kravetz <mike.kravetz@oracle.com>,
Randy Dunlap <rdunlap@infradead.org>,
Vlastimil Babka <vbabka@suse.cz>, Andi Kleen <ak@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Huang Ying <ying.huang@intel.com>,
linux-api@vger.kernel.org
Subject: Re: [RFC PATCH] mm/mempolicy: add MPOL_PREFERRED_STRICT memory policy
Date: Wed, 13 Oct 2021 16:26:28 +0200 [thread overview]
Message-ID: <YWbslIALFQIYNM/g@dhcp22.suse.cz> (raw)
In-Reply-To: <291424a2-c962-533e-c755-e4239fd55f5d@linux.ibm.com>
On Wed 13-10-21 19:27:03, Aneesh Kumar K.V wrote:
[...]
> Another option is to keep this mbind(2) specific and overload flags to be
> the preferred nodeid.
>
> mbind(va, len, MPOL_PREFERRED_STRICT, nodemask, max_node, preferred_node);
First of all I do not think you really want to create a new memory
policy for this. Not to mention that PREFERRED_STRICT is kinda weird in
the first place but one could argue that a preference of the first node
to try is not really specific to BIND/PREFERRED_MANY. Overloading flags
is a nogo.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2021-10-13 14:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 9:45 [RFC PATCH] mm/mempolicy: add MPOL_PREFERRED_STRICT memory policy Aneesh Kumar K.V
2021-10-13 10:42 ` Michal Hocko
2021-10-13 10:48 ` Michal Hocko
2021-10-13 12:35 ` Aneesh Kumar K.V
2021-10-13 12:50 ` Michal Hocko
2021-10-13 12:58 ` Aneesh Kumar K.V
2021-10-13 13:07 ` Michal Hocko
2021-10-13 13:10 ` Aneesh Kumar K.V
2021-10-13 14:22 ` Michal Hocko
2021-10-13 13:57 ` Aneesh Kumar K.V
2021-10-13 14:26 ` Michal Hocko [this message]
2021-10-13 13:16 ` Andi Kleen
2021-10-13 13:23 ` Aneesh Kumar K.V
2021-10-13 14:21 ` Michal Hocko
2021-10-14 9:30 ` Aneesh Kumar K.V
2021-10-14 9:38 ` Michal Hocko
2021-10-14 10:28 ` Aneesh Kumar K.V
2021-10-14 11:41 ` Michal Hocko
2021-10-14 13:29 ` Aneesh Kumar K.V
2021-10-14 14:56 ` Michal Hocko
2021-10-14 15:50 ` Aneesh Kumar K.V
2021-10-19 9:38 ` 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=YWbslIALFQIYNM/g@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mike.kravetz@oracle.com \
--cc=rdunlap@infradead.org \
--cc=vbabka@suse.cz \
--cc=ying.huang@intel.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).