From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id BCB5FC433F5 for ; Mon, 25 Apr 2022 06:11:04 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 24BFD8D0007; Mon, 25 Apr 2022 02:11:04 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 1D52D8D0006; Mon, 25 Apr 2022 02:11:04 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 04DEC8D0007; Mon, 25 Apr 2022 02:11:04 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id E490F8D0006 for ; Mon, 25 Apr 2022 02:11:03 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id BE535626F2 for ; Mon, 25 Apr 2022 06:11:03 +0000 (UTC) X-FDA: 79394378406.16.F447F14 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by imf13.hostedemail.com (Postfix) with ESMTP id 9717F2001E for ; Mon, 25 Apr 2022 06:10:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650867062; x=1682403062; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=2h0S1kU+PSsC6Vl1bnr3IxMhRTqaRHpITQXb+3TY0ss=; b=CV2+Tkk52wtN6bptJMUA5oWnEgeMz2ahVr7MTwNuOMMIsGc4mWr+2Gb+ l48G8mvxUw74nUNVYtxXkjK9PPS1GXNeaqJP73VpY7/85GmAdSWHwxbj5 qe0T8zCIDzIQaYWNleC+DNJuRteeAK2Aur8Qa5CAGXAtqWRPVifHftB+t fEXgBr6VJ0BStcInjH5qVwa85YWfWJpAlhBk6Bw0DnUpMGRPDBn1Cq130 EpDKVS1vccvbQX18eY1TaisQ71o2GW3jETbx07Q8pLLxlMtY0XXVHu4pV 33uxJ2ibQIjn6zb4GHHBEATrzASXSGPRiRX2rsZwDLzXc/wzSUW9SiEs4 Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10327"; a="252516548" X-IronPort-AV: E=Sophos;i="5.90,287,1643702400"; d="scan'208";a="252516548" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Apr 2022 23:11:01 -0700 X-IronPort-AV: E=Sophos;i="5.90,287,1643702400"; d="scan'208";a="557555790" Received: from wupeng-mobl.ccr.corp.intel.com ([10.254.215.115]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 24 Apr 2022 23:10:57 -0700 Message-ID: Subject: Re: [PATCH v2 0/5] mm: demotion: Introduce new node state N_DEMOTION_TARGETS From: "ying.huang@intel.com" To: "Aneesh Kumar K.V" , Jagdish Gediya , Wei Xu , Yang Shi , Dave Hansen , Dan Williams , Davidlohr Bueso Cc: Linux MM , Linux Kernel Mailing List , Andrew Morton , Baolin Wang , Greg Thelen , MichalHocko , Brice Goglin Date: Mon, 25 Apr 2022 14:10:55 +0800 In-Reply-To: <8735i1zurt.fsf@linux.ibm.com> References: <610ccaad03f168440ce765ae5570634f3b77555e.camel@intel.com> <8e31c744a7712bb05dbf7ceb2accf1a35e60306a.camel@intel.com> <78b5f4cfd86efda14c61d515e4db9424e811c5be.camel@intel.com> <200e95cf36c1642512d99431014db8943fed715d.camel@intel.com> <8735i1zurt.fsf@linux.ibm.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 9717F2001E Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=CV2+Tkk5; spf=none (imf13.hostedemail.com: domain of ying.huang@intel.com has no SPF policy when checking 134.134.136.20) smtp.mailfrom=ying.huang@intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspam-User: X-Stat-Signature: mtfb89qotk65k4jtpmxqhff6ycdetu7t X-HE-Tag: 1650867057-172406 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Mon, 2022-04-25 at 09:20 +0530, Aneesh Kumar K.V wrote: > "ying.huang@intel.com" writes: > > > Hi, All, > > > > On Fri, 2022-04-22 at 16:30 +0530, Jagdish Gediya wrote: > > > > [snip] > > > > > I think it is necessary to either have per node demotion targets > > > configuration or the user space interface supported by this patch > > > series. As we don't have clear consensus on how the user interface > > > should look like, we can defer the per node demotion target set > > > interface to future until the real need arises. > > > > > > Current patch series sets N_DEMOTION_TARGET from dax device kmem > > > driver, it may be possible that some memory node desired as demotion > > > target is not detected in the system from dax-device kmem probe path. > > > > > > It is also possible that some of the dax-devices are not preferred as > > > demotion target e.g. HBM, for such devices, node shouldn't be set to > > > N_DEMOTION_TARGETS. In future, Support should be added to distinguish > > > such dax-devices and not mark them as N_DEMOTION_TARGETS from the > > > kernel, but for now this user space interface will be useful to avoid > > > such devices as demotion targets. > > > > > > We can add read only interface to view per node demotion targets > > > from /sys/devices/system/node/nodeX/demotion_targets, remove > > > duplicated /sys/kernel/mm/numa/demotion_target interface and instead > > > make /sys/devices/system/node/demotion_targets writable. > > > > > > Huang, Wei, Yang, > > > What do you suggest? > > > > We cannot remove a kernel ABI in practice. So we need to make it right > > at the first time. Let's try to collect some information for the kernel > > ABI definitation. > > > > The below is just a starting point, please add your requirements. > > > > 1. Jagdish has some machines with DRAM only NUMA nodes, but they don't > > want to use that as the demotion targets. But I don't think this is a > > issue in practice for now, because demote-in-reclaim is disabled by > > default. > > It is not just that the demotion can be disabled. We should be able to > use demotion on a system where we can find DRAM only NUMA nodes. That > cannot be achieved by /sys/kernel/mm/numa/demotion_enabled. It needs > something similar to to N_DEMOTION_TARGETS > Can you show NUMA information of your machines with DRAM-only nodes and PMEM nodes? We can try to find the proper demotion order for the system. If you can not show it, we can defer N_DEMOTION_TARGETS until the machine is available. > > 2. For machines with PMEM installed in only 1 of 2 sockets, for example, > > > > Node 0 & 2 are cpu + dram nodes and node 1 are slow > > memory node near node 0, > > > > available: 3 nodes (0-2) > > node 0 cpus: 0 1 > > node 0 size: n MB > > node 0 free: n MB > > node 1 cpus: > > node 1 size: n MB > > node 1 free: n MB > > node 2 cpus: 2 3 > > node 2 size: n MB > > node 2 free: n MB > > node distances: > > node 0 1 2 > >   0: 10 40 20 > >   1: 40 10 80 > >   2: 20 80 10 > > > > We have 2 choices, > > > > a) > > node demotion targets > > 0 1 > > 2 1 > > This is achieved by > > [PATCH v2 1/5] mm: demotion: Set demotion list differently > > > > > b) > > node demotion targets > > 0 1 > > 2 X > > > > > > a) is good to take advantage of PMEM. b) is good to reduce cross-socket > > traffic. Both are OK as defualt configuration. But some users may > > prefer the other one. So we need a user space ABI to override the > > default configuration. > > > > 3. For machines with HBM (High Bandwidth Memory), as in > > > > https://lore.kernel.org/lkml/39cbe02a-d309-443d-54c9-678a0799342d@gmail.com/ > > > > > [1] local DDR = 10, remote DDR = 20, local HBM = 31, remote HBM = 41 > > > > Although HBM has better performance than DDR, in ACPI SLIT, their > > distance to CPU is longer. We need to provide a way to fix this. The > > user space ABI is one way. The desired result will be to use local DDR > > as demotion targets of local HBM. > > > IMHO the above (2b and 3) can be done using per node demotion targets. Below is > what I think we could do with a single slow memory NUMA node 4. If we can use writable per-node demotion targets as ABI, then we don't need N_DEMOTION_TARGETS. > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 4 > 4 > 4 > > /sys/devices/system/node# echo 1 > node1/demotion_targets > bash: echo: write error: Invalid argument > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 4 > 4 > 4 > > /sys/devices/system/node# echo 0 > node1/demotion_targets > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 0 > 4 > 4 > > /sys/devices/system/node# echo 1 > node0/demotion_targets > bash: echo: write error: Invalid argument > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 0 > 4 > 4 > > Disable demotion for a specific node. > /sys/devices/system/node# echo > node1/demotion_targets > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > > 4 > 4 > > Reset demotion to default > /sys/devices/system/node# echo -1 > node1/demotion_targets > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 4 > 4 > 4 > > When a specific device/NUMA node is used for demotion target via the user interface, it is taken > out of other NUMA node targets. IMHO, we should be careful about interaction between auto-generated and overridden demotion order. Best Regards, Huang, Ying > root@ubuntu-guest:/sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 4 > 4 > 4 > > /sys/devices/system/node# echo 4 > node1/demotion_targets > /sys/devices/system/node# cat node[0-4]/demotion_targets > > 4 > > > > If more than one node requies the same demotion target > /sys/devices/system/node# echo 4 > node0/demotion_targets > /sys/devices/system/node# cat node[0-4]/demotion_targets > 4 > 4 > > > > -aneesh