From: huang ying <huang.ying.caritas@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Wei Xu <weixugc@google.com>, Huang Ying <ying.huang@intel.com>,
Yang Shi <shy828301@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim C Chen <tim.c.chen@intel.com>,
Michal Hocko <mhocko@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hesham Almatary <hesham.almatary@huawei.com>,
Dave Hansen <dave.hansen@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
jvgediya.oss@gmail.com, Bharata B Rao <bharata@amd.com>
Subject: Re: [PATCH v14 01/10] mm/demotion: Add support for explicit memory tiers
Date: Tue, 16 Aug 2022 16:28:51 +0800 [thread overview]
Message-ID: <CAC=cRTNDN7mHvHfk=bSN5SDUY864+1EOAOAg6Wd030ENWfY+fg@mail.gmail.com> (raw)
In-Reply-To: <20220812055710.357820-2-aneesh.kumar@linux.ibm.com>
On Fri, Aug 12, 2022 at 1:58 PM Aneesh Kumar K.V
<aneesh.kumar@linux.ibm.com> wrote:
[snip]
> diff --git a/include/linux/memory-tiers.h b/include/linux/memory-tiers.h
> new file mode 100644
> index 000000000000..bc7c1b799bef
> --- /dev/null
> +++ b/include/linux/memory-tiers.h
> @@ -0,0 +1,15 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +#ifndef _LINUX_MEMORY_TIERS_H
> +#define _LINUX_MEMORY_TIERS_H
> +
> +/*
> + * Each tier cover a abstrace distance chunk size of 128
> + */
> +#define MEMTIER_CHUNK_BITS 7
> +#define MEMTIER_CHUNK_SIZE (1 << MEMTIER_CHUNK_BITS)
> +/*
> + * Smaller abstract distance value imply faster(higher) memory tiers.
> + */
> +#define MEMTIER_ADISTANCE_DRAM (4 * MEMTIER_CHUNK_SIZE)
This will make the abstract distance of DRAM the start of its memory
tier. So that any memory type that is slightly slower than DRAM will
be put in a lower memory tier. So I think it's better to put the DRAM
at the middle of its memory tier by default. For example,
4 * MEMTIER_CHUNK_SIZE + MEMTIER_CHUNK_SIZE / 2
> +
> +#endif /* _LINUX_MEMORY_TIERS_H */
[snip]
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2022-08-16 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 5:56 [PATCH v14 00/10] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 01/10] mm/demotion: Add support for explicit memory tiers Aneesh Kumar K.V
2022-08-16 8:28 ` huang ying [this message]
2022-08-12 5:57 ` [PATCH v14 02/10] mm/demotion: Move memory demotion related code Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 03/10] mm/demotion: Add hotplug callbacks to handle new numa node onlined Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 04/10] mm/demotion/dax/kmem: Set node's abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE Aneesh Kumar K.V
2022-08-15 2:25 ` Huang, Ying
2022-08-15 2:39 ` Huang, Ying
2022-08-16 5:09 ` Aneesh Kumar K V
2022-08-16 7:28 ` huang ying
2022-08-16 8:12 ` Bharata B Rao
2022-08-16 8:26 ` huang ying
2022-08-16 14:45 ` Bharata B Rao
2022-08-17 1:02 ` Huang, Ying
2022-08-12 5:57 ` [PATCH v14 05/10] mm/demotion: Build demotion targets based on explicit memory tiers Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 06/10] mm/demotion: Add pg_data_t member to track node memory tier details Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 07/10] mm/demotion: Drop memtier from memtype Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 08/10] mm/demotion: Demote pages according to allocation fallback order Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 09/10] mm/demotion: Update node_is_toptier to work with memory tiers Aneesh Kumar K.V
2022-08-12 5:57 ` [PATCH v14 10/10] lib/nodemask: Optimize node_random for nodemask with single NUMA node Aneesh Kumar K.V
2022-08-15 2:49 ` [PATCH v14 00/10] mm/demotion: Memory tiers and demotion Huang, Ying
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='CAC=cRTNDN7mHvHfk=bSN5SDUY864+1EOAOAg6Wd030ENWfY+fg@mail.gmail.com' \
--to=huang.ying.caritas@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--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=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shy828301@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox