Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp154914rdb; Tue, 5 Dec 2023 01:14:58 -0800 (PST) X-Google-Smtp-Source: AGHT+IFgCekNoK4pL+bxBi0jp639FH1O+8b8ZlIgq/7xSU0XFEykhl458u2Iw4hlcCwq/WyqSgVF X-Received: by 2002:a05:6358:281e:b0:16f:f32c:1d96 with SMTP id k30-20020a056358281e00b0016ff32c1d96mr2300896rwb.29.1701767697862; Tue, 05 Dec 2023 01:14:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701767697; cv=none; d=google.com; s=arc-20160816; b=DWFQaFTixgj6ireGSUXyRmPWjnZikfdanLy2LBl1v0O+lx9vwvWe/PF7kLNJs8LObX F8sliQk360JhUcxM6OPtd12hp5Ia8h0k+hz5Ii07JoQrzGtqZYSSFrG/PSvWJHQ7lqHw NcSDIjfj2CbwWtTkYJRXrSJYyWSc8yW+CSRpesqYCGKu+5OtYYyuUSTJUFX+nwwsbQkg Q3oJWGLHHN6d+a6U6/Lkr1hUrG1alGj8XphVAUWCJwlTcSq8ts9Qi19w0wFjiE5syEKj 7T6tfMcgGtWSfqInoAPI00zY+KXv0dpMVLwPab3IHnybRSVpCGny5iLSCLOBIcroSCFO +wuA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:dkim-signature; bh=TXbquVkk/w+VKDACbX8Ub7fengeNjZRLquLOxbwfCs0=; fh=VSnhXHqfUZ3cScTa15g9Sizr5oGNx4Fn/XxU17RwpXA=; b=tdIh5Bz1Rl5/eXzVaF021VlLBhc/62pRckqJyP3OTsDIkCwCQZtbQkF6hUTDN1a+xK pjromHCyk/aF+wECZDrMkbaorxKBE7xk3WPEd3t8Ds5/dJoicEgTI36zYnEWwheiH5wm TQIgFt084McUAUel8SGG8mV50rc5Wg7eUsCSZavqwY53SoGXZnlTbY33GggqHttaGSq1 HS1b4wmPx/KBnRXCd+RcAxMhDCUxkjcEGJVf+JTyYNHHzhZ+sEwbvTKZzSafodMCYRjF WxXtp69bIFDiOGSAfsG7LRrVK7jhbB8u3vkJ0XulNL9Jzdd9ZT4YyNvFd3AiQKIUjjYr fDeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Smr6v6TK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from snail.vger.email (snail.vger.email. [23.128.96.37]) by mx.google.com with ESMTPS id q7-20020a634307000000b005c18dd91684si9395771pga.352.2023.12.05.01.14.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 05 Dec 2023 01:14:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) client-ip=23.128.96.37; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Smr6v6TK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.37 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by snail.vger.email (Postfix) with ESMTP id D97AF80B8E75; Tue, 5 Dec 2023 01:14:56 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at snail.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231852AbjLEJOo (ORCPT + 99 others); Tue, 5 Dec 2023 04:14:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48344 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231862AbjLEJOn (ORCPT ); Tue, 5 Dec 2023 04:14:43 -0500 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.10]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 293CF188; Tue, 5 Dec 2023 01:14:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1701767689; x=1733303689; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=CA/po2UEZKXyste1mfpEbd51SPSYNHn4HvETMXvX/SU=; b=Smr6v6TKfVuq3yl4xw1gssOdnZ47e021ubxpp/C2GZPv//U4lRjQMMXp oncqU/rJeI0AvoEtQaFbvq7jafz+43z/yW2MEzN5ZIvMk+oMYA9vbr9xF +P9nWmM5xLSgeV+UM7bBoZ3Jth+koD/rbFs3nmdFVMxLEnFaMQiaJHTT/ KPGbNdFYYrrG37kGyzPlQPK1j7JnBNuIXAMsoMfZyDT/rKZsln3kRN+du lUinTdlSBqqKYGInTDW/yRRE1r0tY2Fe6XyyiPXTi0uNRngJKSj4VeTO9 jRa8ohQwYCoIwf6cx/SADYlvT6ylYgUX4RtNN2y8fBKfe/RHcW2MSRKff g==; X-IronPort-AV: E=McAfee;i="6600,9927,10914"; a="945217" X-IronPort-AV: E=Sophos;i="6.04,251,1695711600"; d="scan'208";a="945217" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by fmvoesa104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Dec 2023 01:14:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.04,251,1695711600"; d="scan'208";a="18895366" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.238.208.55]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Dec 2023 01:14:44 -0800 From: "Huang, Ying" To: Srinivasulu Thanneeru Cc: Michal Hocko , , , , , , , , , , , , , , , , , , Subject: Re: [EXT] Re: [RFC PATCH 0/2] Node migration between memory tiers In-Reply-To: <1db561a9-6984-418d-9305-a2a5ece93696@micron.com> (Srinivasulu Thanneeru's message of "Tue, 5 Dec 2023 01:26:07 +0530") References: <20231130220422.2033-1-sthanneeru.opensrc@micron.com> <1db561a9-6984-418d-9305-a2a5ece93696@micron.com> Date: Tue, 05 Dec 2023 17:12:43 +0800 Message-ID: <87a5qp2et0.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (snail.vger.email [0.0.0.0]); Tue, 05 Dec 2023 01:14:57 -0800 (PST) Srinivasulu Thanneeru writes: > 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 >>> >>> 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. > > 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. The case 2 reminds me a RFC before as follows, https://lore.kernel.org/linux-mm/20221027065925.476955-1-ying.huang@intel.com/ The basic idea behind is that do we really need to put NUMA nodes with different performance metrics in one memory tier? Are there use cases? Will we have a system with so many different types of memory? As in your case, you don't want to put DRAM and CXL memory in one memory tier. Do you think we will need to put two types of memory in one memory tier? -- Best Regards, Huang, Ying