From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: akpm@linux-foundation.org, ying.huang@intel.com,
dave.hansen@linux.intel.com
Cc: ziy@nvidia.com, osalvador@suse.de, shy828301@gmail.com,
baolin.wang@linux.alibaba.com, zhongjiang-ali@linux.alibaba.com,
xlpang@linux.alibaba.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] Support multiple target nodes demotion
Date: Thu, 11 Nov 2021 15:48:33 +0800 [thread overview]
Message-ID: <cover.1636616548.git.baolin.wang@linux.alibaba.com> (raw)
Hi,
This patch set is used to support multiple target nodes demotion
if a system has multiple slow memory nodes. Please help to review.
Thanks.
Changes from v1:
- Add a new patch to allocate the node_demotion dynamically.
- Update some comments.
- Simplify some variables' name.
Changes from RFC v2:
- Change to 'short' type for target nodes array.
- Remove nodemask instead selecting target node directly.
- Add WARN_ONCE() if the target nodes exceed the maximum value.
Changes from RFC v1:
- Re-define the node_demotion structure.
- Set up multiple target nodes by validating the node distance.
- Add more comments.
Baolin Wang (2):
mm: migrate: Support multiple target nodes demotion
mm: migrate: Allocate the node_demotion structure dynamically
mm/migrate.c | 158 +++++++++++++++++++++++++++++++++++++++++++++--------------
1 file changed, 122 insertions(+), 36 deletions(-)
--
1.8.3.1
next reply other threads:[~2021-11-11 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 7:48 Baolin Wang [this message]
2021-11-11 7:48 ` [PATCH v2 1/2] mm: migrate: " Baolin Wang
2021-11-11 8:20 ` Huang, Ying
2021-11-11 10:52 ` Baolin Wang
2021-11-11 7:48 ` [PATCH v2 2/2] mm: migrate: Allocate the node_demotion structure dynamically Baolin Wang
2021-11-11 8:51 ` Huang, Ying
2021-11-11 11:20 ` Baolin Wang
2021-11-11 23:39 ` Huang, Ying
2021-11-11 13:42 ` kernel test robot
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=cover.1636616548.git.baolin.wang@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=shy828301@gmail.com \
--cc=xlpang@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zhongjiang-ali@linux.alibaba.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