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 7353DC433EF for ; Thu, 21 Apr 2022 07:29:50 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 084586B0071; Thu, 21 Apr 2022 03:29:50 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 032496B0073; Thu, 21 Apr 2022 03:29:49 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id E3C426B0074; Thu, 21 Apr 2022 03:29:49 -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 D343A6B0071 for ; Thu, 21 Apr 2022 03:29:49 -0400 (EDT) Received: from smtpin03.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id A7B2725E2D for ; Thu, 21 Apr 2022 07:29:49 +0000 (UTC) X-FDA: 79380061698.03.1448040 Received: from mail-vs1-f44.google.com (mail-vs1-f44.google.com [209.85.217.44]) by imf23.hostedemail.com (Postfix) with ESMTP id 0A246140027 for ; Thu, 21 Apr 2022 07:29:46 +0000 (UTC) Received: by mail-vs1-f44.google.com with SMTP id r1so3734750vsi.12 for ; Thu, 21 Apr 2022 00:29:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0Kef+uraHlTS1J8sntjcDuAazHDLlgQ9ZX8fx3bltn4=; b=MJoHzYG/QyhL2BlIJO/TiCWwz52LYDroJq+MKWPLxEwZg9G4VVPzP22pMcbq9h2LXu l0MJ3TFbvLjP6xW0Ksn0FmdKtZ5pSOohjkX8GiOi32S20ZbmRPhpvX7G5OhXRyGzUtlX x3kLRTd8v4nkRqN3I/6/YZ1urnXkgajFJE4wekTmT168NeBFhMHEGfglOa65L9VE1fYZ Lb/kr2bD06LHjq0V5HoZnlmSkLuKMomwW0Ag3Owi1kRwg8wz0luHSgKDH1j0rKV1tJV8 16I+v0qL16fEi2sWPF3JUPfbHFwBQVNT7/ssh/N8G3orl2uQYjQ9sLMh9FnYQKlnN0cj KFGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0Kef+uraHlTS1J8sntjcDuAazHDLlgQ9ZX8fx3bltn4=; b=VUJf1h3Omwfcgs5BFTAFXhBk3S3bT86I37r9QMzKplX7G+q0njpjODsKroXlVzaOup 0YZmc5NLH1hT93tqbYgyw5pmjfjcRQlw8u+liBMiVQ5PxUKBabrhf3AwTp+38ivcPzL7 DBjKlS9Gfnk6mr07mA3Nq+mG3+LVY2O3N+NfIzEHlVY6s2zqMz9O1Z1hAzb1xu6MZqHA aN6wycHbHWNfrX7mgGFZxk/0ZKjrP28tpVyxdRXHE3yPpTNdkhR7tD6mMThlLbEuRa72 wHETwZuKUIYkDFcH/PLZhO4H3WGQQGbViTwHE+Sk9he6l7PYHn1zi5+riS6BzL4173U+ JbXA== X-Gm-Message-State: AOAM531jWtthjlJek9lI36vecILbRZ2nPsgvypytZ0ncN50m5Tx9865V mxbrcpRXErBJmslQDKsegqfmfvjDP5NKxQTkGLmQtQ== X-Google-Smtp-Source: ABdhPJzkKB+LUQi4523knJPyGMlsVupJhV+Ljr5mwRn69w5lchSOWSy7mTCK/ecP+CFyRnkobtAYI06B7o9keINQepI= X-Received: by 2002:a05:6102:3106:b0:32a:18c8:1633 with SMTP id e6-20020a056102310600b0032a18c81633mr7733600vsh.51.1650526188028; Thu, 21 Apr 2022 00:29:48 -0700 (PDT) MIME-Version: 1.0 References: <20220413092206.73974-1-jvgediya@linux.ibm.com> <6365983a8fbd8c325bb18959c51e9417fd821c91.camel@intel.com> In-Reply-To: From: Wei Xu Date: Thu, 21 Apr 2022 00:29:37 -0700 Message-ID: Subject: Re: [PATCH v2 0/5] mm: demotion: Introduce new node state N_DEMOTION_TARGETS To: "ying.huang@intel.com" Cc: Yang Shi , Jagdish Gediya , Linux MM , Linux Kernel Mailing List , Andrew Morton , "Aneesh Kumar K.V" , Baolin Wang , Dave Hansen , Dan Williams , Greg Thelen Content-Type: text/plain; charset="UTF-8" X-Rspam-User: X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 0A246140027 X-Stat-Signature: e5oi84tjjb7nm4fj5czqhhqiu1gup1z6 Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b="MJoHzYG/"; spf=pass (imf23.hostedemail.com: domain of weixugc@google.com designates 209.85.217.44 as permitted sender) smtp.mailfrom=weixugc@google.com; dmarc=pass (policy=reject) header.from=google.com X-HE-Tag: 1650526186-782812 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 Thu, Apr 21, 2022 at 12:08 AM ying.huang@intel.com wrote: > > On Wed, 2022-04-20 at 23:49 -0700, Wei Xu wrote: > > On Wed, Apr 20, 2022 at 11:24 PM ying.huang@intel.com > > wrote: > > > > > > On Wed, 2022-04-20 at 22:41 -0700, Wei Xu wrote: > > > > On Wed, Apr 20, 2022 at 8:12 PM Yang Shi wrote: > > > > > > > > > > On Thu, Apr 14, 2022 at 12:00 AM ying.huang@intel.com > > > > > wrote: > > > > > > > > > > > > On Wed, 2022-04-13 at 14:52 +0530, Jagdish Gediya wrote: > > > > > > > Current implementation to find the demotion targets works > > > > > > > based on node state N_MEMORY, however some systems may have > > > > > > > dram only memory numa node which are N_MEMORY but not the > > > > > > > right choices as demotion targets. > > > > > > > > > > > > > > This patch series introduces the new node state > > > > > > > N_DEMOTION_TARGETS, which is used to distinguish the nodes which > > > > > > > can be used as demotion targets, node_states[N_DEMOTION_TARGETS] > > > > > > > is used to hold the list of nodes which can be used as demotion > > > > > > > targets, support is also added to set the demotion target > > > > > > > list from user space so that default behavior can be overridden. > > > > > > > > > > > > It appears that your proposed user space interface cannot solve all > > > > > > problems. For example, for system as follows, > > > > > > > > > > > > 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 > > > > > > > > > > > > Demotion order 1: > > > > > > > > > > > > node demotion_target > > > > > > 0 1 > > > > > > 1 X > > > > > > 2 X > > > > > > > > > > > > Demotion order 2: > > > > > > > > > > > > node demotion_target > > > > > > 0 1 > > > > > > 1 X > > > > > > 2 1 > > > > > > > > > > > > The demotion order 1 is preferred if we want to reduce cross-socket > > > > > > traffic. While the demotion order 2 is preferred if we want to take > > > > > > full advantage of the slow memory node. We can take any choice as > > > > > > automatic-generated order, while make the other choice possible via user > > > > > > space overridden. > > > > > > > > > > > > I don't know how to implement this via your proposed user space > > > > > > interface. How about the following user space interface? > > > > > > > > > > > > 1. Add a file "demotion_order_override" in > > > > > > /sys/devices/system/node/ > > > > > > > > > > > > 2. When read, "1" is output if the demotion order of the system has been > > > > > > overridden; "0" is output if not. > > > > > > > > > > > > 3. When write "1", the demotion order of the system will become the > > > > > > overridden mode. When write "0", the demotion order of the system will > > > > > > become the automatic mode and the demotion order will be re-generated. > > > > > > > > > > > > 4. Add a file "demotion_targets" for each node in > > > > > > /sys/devices/system/node/nodeX/ > > > > > > > > > > > > 5. When read, the demotion targets of nodeX will be output. > > > > > > > > > > > > 6. When write a node list to the file, the demotion targets of nodeX > > > > > > will be set to the written nodes. And the demotion order of the system > > > > > > will become the overridden mode. > > > > > > > > > > TBH I don't think having override demotion targets in userspace is > > > > > quite useful in real life for now (it might become useful in the > > > > > future, I can't tell). Imagine you manage hundred thousands of > > > > > machines, which may come from different vendors, have different > > > > > generations of hardware, have different versions of firmware, it would > > > > > be a nightmare for the users to configure the demotion targets > > > > > properly. So it would be great to have the kernel properly configure > > > > > it *without* intervening from the users. > > > > > > > > > > So we should pick up a proper default policy and stick with that > > > > > policy unless it doesn't work well for the most workloads. I do > > > > > understand it is hard to make everyone happy. My proposal is having > > > > > every node in the fast tier has a demotion target (at least one) if > > > > > the slow tier exists sounds like a reasonable default policy. I think > > > > > this is also the current implementation. > > > > > > > > > > > > > This is reasonable. I agree that with a decent default policy, > > > > > > > > > > I agree that a decent default policy is important. As that was enhanced > > > in [1/5] of this patchset. > > > > > > > the > > > > overriding of per-node demotion targets can be deferred. The most > > > > important problem here is that we should allow the configurations > > > > where memory-only nodes are not used as demotion targets, which this > > > > patch set has already addressed. > > > > > > Do you mean the user space interface proposed by [3/5] of this patchset? > > > > Yes. > > > > > IMHO, if we want to add a user space interface, I think that it should > > > be powerful enough to address all existing issues and some potential > > > future issues, so that it can be stable. I don't think it's a good idea > > > to define a partial user space interface that works only for a specific > > > use case and cannot be extended for other use cases. > > > > I actually think that they can be viewed as two separate problems: one > > is to define which nodes can be used as demotion targets (this patch > > set), and the other is how to initialize the per-node demotion path > > (node_demotion[]). We don't have to solve both problems at the same > > time. > > > > If we decide to go with a per-node demotion path customization > > interface to indirectly set N_DEMOTION_TARGETS, I'd prefer that there > > is a single global control to turn off all demotion targets (for the > > machines that don't use memory-only nodes for demotion). > > > > There's one already. In commit 20b51af15e01 ("mm/migrate: add sysfs > interface to enable reclaim migration"), a sysfs interface > > /sys/kernel/mm/numa/demotion_enabled > > is added to turn off all demotion targets. IIUC, this sysfs interface only turns off demotion-in-reclaim. It will be even cleaner if we have an easy way to clear node_demotion[] and N_DEMOTION_TARGETS so that the userspace (post-boot agent, not init scripts) can know that the machine doesn't even have memory tiering hardware enabled. > Best Regards, > Huang, Ying > > >