Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:2 as permitted sender) client-ip=2620:137:e000::3:2;
Date:   Tue, 5 Dec 2023 09:35:44 +0100
From:   Michal Hocko <mhocko@suse.com>
To:     Srinivasulu Thanneeru <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: [EXT] Re: [RFC PATCH 0/2] Node migration between memory tiers
Message-ID: <ZW7g4ExYF79gMEBU@tiehlicka>
References: <20231130220422.2033-1-sthanneeru.opensrc@micron.com>
 <ZW3zl2Fke5FtQCv3@tiehlicka>
 <1db561a9-6984-418d-9305-a2a5ece93696@micron.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1db561a9-6984-418d-9305-a2a5ece93696@micron.com>
Precedence: bulk

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?
-- 
Michal Hocko
SUSE Labs