LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Gang Li <ligang.bdlg@bytedance.com>
To: feng.tang@intel.com
Cc: linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v7 0/5] Introduce multi-preference mempolicy
Date: Wed, 1 Dec 2021 11:09:18 +0800 [thread overview]
Message-ID: <b0d1f682-6868-c5f6-631c-2da93ee2b479@bytedance.com> (raw)
In-Reply-To: <1627970362-61305-1-git-send-email-feng.tang@intel.com>
Hi Feng:
I am a little confused:
We have `MPOL_PREFERRED`, why you introduce `MPOL_PREFERRED_MANY`
instead of making `MPOL_PREFERRED` support multiple preferred nodes?
--
Thanks
Gang Li
next prev parent reply other threads:[~2021-12-01 3:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 5:59 [PATCH v7 0/5] Introduce multi-preference mempolicy Feng Tang
2021-08-03 5:59 ` [PATCH v7 1/5] mm/mempolicy: Add MPOL_PREFERRED_MANY for multiple preferred nodes Feng Tang
2021-08-06 13:27 ` Michal Hocko
2021-08-06 13:28 ` Michal Hocko
2021-08-03 5:59 ` [PATCH v7 2/5] mm/memplicy: add page allocation function for MPOL_PREFERRED_MANY policy Feng Tang
2021-08-06 13:29 ` Michal Hocko
2021-08-03 5:59 ` [PATCH v7 3/5] mm/hugetlb: add support for mempolicy MPOL_PREFERRED_MANY Feng Tang
2021-08-06 13:35 ` Michal Hocko
2021-08-09 2:44 ` Feng Tang
2021-08-09 8:41 ` Michal Hocko
2021-08-09 12:37 ` Feng Tang
2021-08-09 13:19 ` Michal Hocko
2021-08-10 8:50 ` Feng Tang
2021-08-10 21:35 ` Hugh Dickins
2021-08-11 1:37 ` Feng Tang
2021-08-10 20:06 ` [PATCH] mm/hugetlb: Initialize page to NULL in alloc_buddy_huge_page_with_mpol() Nathan Chancellor
2021-08-11 1:21 ` Feng Tang
2021-08-03 5:59 ` [PATCH v7 4/5] mm/mempolicy: Advertise new MPOL_PREFERRED_MANY Feng Tang
2021-08-03 5:59 ` [PATCH v7 5/5] mm/mempolicy: unify the create() func for bind/interleave/prefer-many policies Feng Tang
2021-12-01 3:09 ` Gang Li [this message]
2021-12-01 5:33 ` [PATCH v7 0/5] Introduce multi-preference mempolicy Feng Tang
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=b0d1f682-6868-c5f6-631c-2da93ee2b479@bytedance.com \
--to=ligang.bdlg@bytedance.com \
--cc=1627970362-61305-1-git-send-email-feng.tang@intel.com \
--cc=feng.tang@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).