From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, ying.huang@intel.com,
weixugc@google.com, tim.c.chen@intel.com, sj@kernel.org,
shy828301@gmail.com, mhocko@kernel.org, jvgediya.oss@gmail.com,
Jonathan.Cameron@huawei.com, hesham.almatary@huawei.com,
hannes@cmpxchg.org, dave@stgolabs.net, dave.hansen@intel.com,
dan.j.williams@intel.com, bharata@amd.com, apopple@nvidia.com,
aneesh.kumar@linux.ibm.com, akpm@linux-foundation.org
Subject: [folded-merged] mm-demotion-update-node_is_toptier-to-work-with-memory-tiers-fix-3.patch removed from -mm tree
Date: Mon, 26 Sep 2022 13:59:26 -0700 [thread overview]
Message-ID: <20220926205927.71BFAC433D6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/demotion: make toptier_distance inclusive upper bound of toptiers
has been removed from the -mm tree. Its filename was
mm-demotion-update-node_is_toptier-to-work-with-memory-tiers-fix-3.patch
This patch was dropped because it was folded into mm-demotion-update-node_is_toptier-to-work-with-memory-tiers.patch
------------------------------------------------------
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: mm/demotion: make toptier_distance inclusive upper bound of toptiers
Date: Tue, 30 Aug 2022 13:44:57 +0530
Based on suggestion from Wei Xu, having an inclusive upper bound is
simpler.
Link: https://lkml.kernel.org/r/20220830081457.118960-1-aneesh.kumar@linux.ibm.com
Fixes: mm/demotion: Update node_is_toptier to work with memory tiers
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Cc: Alistair Popple <apopple@nvidia.com>
Cc: Bharata B Rao <bharata@amd.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Hansen <dave.hansen@intel.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>
Cc: Hesham Almatary <hesham.almatary@huawei.com>
Cc: "Huang, Ying" <ying.huang@intel.com>
Cc: Jagdish Gediya <jvgediya.oss@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Michal Hocko <mhocko@kernel.org>
Cc: SeongJae Park <sj@kernel.org>
Cc: Tim Chen <tim.c.chen@intel.com>
Cc: Wei Xu <weixugc@google.com>
Cc: Yang Shi <shy828301@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory-tiers.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--- a/mm/memory-tiers.c~mm-demotion-update-node_is_toptier-to-work-with-memory-tiers-fix-3
+++ a/mm/memory-tiers.c
@@ -179,7 +179,7 @@ bool node_is_toptier(int node)
toptier = true;
goto out;
}
- if (memtier->adistance_start < top_tier_adistance)
+ if (memtier->adistance_start <= top_tier_adistance)
toptier = true;
else
toptier = false;
@@ -361,7 +361,8 @@ static void establish_demotion_targets(v
* abstract distance below the max value of this memtier
* is considered toptier.
*/
- top_tier_adistance = memtier->adistance_start + MEMTIER_CHUNK_SIZE;
+ top_tier_adistance = memtier->adistance_start +
+ MEMTIER_CHUNK_SIZE - 1;
break;
}
}
_
Patches currently in -mm which might be from aneesh.kumar@linux.ibm.com are
mm-demotion-add-support-for-explicit-memory-tiers.patch
mm-demotion-move-memory-demotion-related-code.patch
mm-demotion-add-hotplug-callbacks-to-handle-new-numa-node-onlined.patch
mm-demotion-dax-kmem-set-nodes-abstract-distance-to-memtier_default_dax_adistance.patch
mm-demotion-build-demotion-targets-based-on-explicit-memory-tiers.patch
mm-demotion-add-pg_data_t-member-to-track-node-memory-tier-details.patch
mm-demotion-drop-memtier-from-memtype.patch
mm-demotion-update-node_is_toptier-to-work-with-memory-tiers.patch
lib-nodemask-optimize-node_random-for-nodemask-with-single-numa-node.patch
mm-demotion-expose-memory-tier-details-via-sysfs.patch
mm-demotion-expose-memory-tier-details-via-sysfs-v4.patch
reply other threads:[~2022-09-26 20:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220926205927.71BFAC433D6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=bharata@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya.oss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shy828301@gmail.com \
--cc=sj@kernel.org \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.