Linux CXL
 help / color / mirror / Atom feed
From: Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
To: Michal Hocko <mhocko@suse.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: [EXT] Re: [RFC PATCH 0/2] Node migration between memory tiers
Date: Tue, 5 Dec 2023 14:12:17 +0530	[thread overview]
Message-ID: <2552828e-6865-4fa8-a9c4-8ed76dd85257@micron.com> (raw)
In-Reply-To: <ZW7g4ExYF79gMEBU@tiehlicka>



On 12/5/2023 2:05 PM, Michal Hocko wrote:
> CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you recognize the sender and were expecting this message.
> 
> 
> On Tue 05-12-23 01:26:07, Srinivasulu Thanneeru wrote:
>>
>>
>> On 12/4/2023 9:13 PM, Michal Hocko wrote:
>>> CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you recognize the sender and were expecting this message.
>>>
>>>
>>> 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?
>>
>> Hi Michal Hock,
>>
>> Following two use-cases we have observed.
>> 1. It is not accurate to group similar memory types in the same tier,
>>     because even similar memory types may have different speed grades.
> 
> Presumably they are grouped based on a HW configuration. Does that mean
> that the configuration is wrong? Are you trying to workaround that by
> this interface?
> 
>> 2. Some systems boots up with CXL devices and DRAM on the same memory-tier,
>> we need a way to move the CXL nodes to the correct tier from the user space.
> 
> Again, could you expand a bit more and explain why this cannot be
> configured automatically?

Yes, in both cases above, if hardware not automatically populated 
properly, in that case this interface would help to correct it from user 
space.

We had observed case-2 in our setups.

> --
> Michal Hocko
> SUSE Labs

  reply	other threads:[~2023-12-05  8:42 UTC|newest]

Thread overview: 14+ 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-11-30 22:04 ` [RFC PATCH 2/2] memory tier: Support node migration between tiers sthanneeru.opensrc
2023-12-04 15:43 ` [RFC PATCH 0/2] Node migration between memory tiers Michal Hocko
2023-12-04 19:56   ` [EXT] " Srinivasulu Thanneeru
2023-12-05  8:35     ` Michal Hocko
2023-12-05  8:42       ` Srinivasulu Thanneeru [this message]
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

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=2552828e-6865-4fa8-a9c4-8ed76dd85257@micron.com \
    --to=sthanneeru.opensrc@micron.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=mhocko@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox