From: Michal Hocko <mhocko@suse.com>
To: sthanneeru.opensrc@micron.com
Cc: aneesh.kumar@linux.ibm.com, linux-cxl@vger.kernel.org,
linux-mm@kvack.org, dan.j.williams@intel.com, hannes@cmpxchg.org,
hasanalmaruf@fb.com, haowang3@fb.com, ying.huang@intel.com,
gregory.price@memverge.com, tj@kernel.org,
hezhongkun.hzk@bytedance.com, fvdl@google.com,
john@jagalactic.com, emirakhur@micron.com,
vtavarespetr@micron.com, Ravis.OpenSrc@micron.com,
Jonathan.Cameron@huawei.com, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Node migration between memory tiers
Date: Mon, 4 Dec 2023 16:43:19 +0100 [thread overview]
Message-ID: <ZW3zl2Fke5FtQCv3@tiehlicka> (raw)
In-Reply-To: <20231130220422.2033-1-sthanneeru.opensrc@micron.com>
On Fri 01-12-23 03:34:20, sthanneeru.opensrc@micron.com wrote:
> From: Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
>
> The memory tiers feature allows nodes with similar memory types
> or performance characteristics to be grouped together in a
> memory tier. However, there is currently no provision for
> moving a node from one tier to another on demand.
Could you expand on why this is really needed/necessary? What is the
actual usecase?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2023-12-04 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 22:04 [RFC PATCH 0/2] Node migration between memory tiers sthanneeru.opensrc
2023-11-30 22:04 ` [RFC PATCH 1/2] base/node: Add sysfs for adistance_offset sthanneeru.opensrc
2023-12-05 18:29 ` kernel test robot
2023-11-30 22:04 ` [RFC PATCH 2/2] memory tier: Support node migration between tiers sthanneeru.opensrc
2023-12-04 15:43 ` Michal Hocko [this message]
2023-12-04 19:56 ` [EXT] Re: [RFC PATCH 0/2] Node migration between memory tiers Srinivasulu Thanneeru
2023-12-05 8:35 ` Michal Hocko
2023-12-05 8:42 ` Srinivasulu Thanneeru
2023-12-05 8:51 ` Michal Hocko
2023-12-05 9:02 ` Srinivasulu Thanneeru
2023-12-05 9:09 ` Michal Hocko
2023-12-05 9:19 ` Ravi Jonnalagadda
2023-12-06 15:22 ` Michal Hocko
2023-12-05 8:51 ` [EXT] " Huang, Ying
2023-12-05 9:12 ` Huang, Ying
-- strict thread matches above, loose matches on Subject: below --
2023-11-30 21:48 sthanneeru.opensrc
2023-12-04 8:52 ` 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=ZW3zl2Fke5FtQCv3@tiehlicka \
--to=mhocko@suse.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Ravis.OpenSrc@micron.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=emirakhur@micron.com \
--cc=fvdl@google.com \
--cc=gregory.price@memverge.com \
--cc=hannes@cmpxchg.org \
--cc=haowang3@fb.com \
--cc=hasanalmaruf@fb.com \
--cc=hezhongkun.hzk@bytedance.com \
--cc=john@jagalactic.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sthanneeru.opensrc@micron.com \
--cc=tj@kernel.org \
--cc=vtavarespetr@micron.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.