linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: akpm@linux-foundation.org
Cc: david@redhat.com, mgorman@techsingularity.net,
	wangkefeng.wang@huawei.com, jhubbard@nvidia.com,
	ying.huang@intel.com, 21cnbao@gmail.com, ryan.roberts@arm.com,
	baolin.wang@linux.alibaba.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] support multi-size THP numa balancing
Date: Fri, 29 Mar 2024 14:56:44 +0800	[thread overview]
Message-ID: <cover.1711683069.git.baolin.wang@linux.alibaba.com> (raw)

This patchset tries to support mTHP numa balancing, as a simple solution
to start, the NUMA balancing algorithm for mTHP will follow the THP strategy
as the basic support. Please find details in each patch.

Changes from v1:
 - Fix the issue where the end address might exceed the range of the
folio size, suggested by Huang, Ying.
 - Simplify the folio validation.
 - Add pte_modify() before checking pte writable.
 - Update the performance data.

Changes from RFC v2:
 - Follow the THP algorithm per Huang, Ying.

Changes from RFC v1:
 - Add some preformance data per Huang, Ying.
 - Allow mTHP scanning per David Hildenbrand.
 - Avoid sharing mapping for numa balancing to avoid false sharing.
 - Add more commit message.

Baolin Wang (2):
  mm: factor out the numa mapping rebuilding into a new helper
  mm: support multi-size THP numa balancing

 mm/memory.c   | 77 +++++++++++++++++++++++++++++++++++++++++----------
 mm/mprotect.c |  3 +-
 2 files changed, 65 insertions(+), 15 deletions(-)

-- 
2.39.3



             reply	other threads:[~2024-03-29  6:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29  6:56 Baolin Wang [this message]
2024-03-29  6:56 ` [PATCH v2 1/2] mm: factor out the numa mapping rebuilding into a new helper Baolin Wang
2024-03-29  6:56 ` [PATCH v2 2/2] mm: support multi-size THP numa balancing Baolin Wang
2024-04-01  2:50   ` Huang, Ying
2024-04-01  9:43     ` Baolin Wang
2024-04-01  3:47   ` Kefeng Wang
2024-04-01  9:47     ` Baolin Wang

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.1711683069.git.baolin.wang@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=ryan.roberts@arm.com \
    --cc=wangkefeng.wang@huawei.com \
    --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).