Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6484404imu; Wed, 30 Jan 2019 15:54:33 -0800 (PST) X-Google-Smtp-Source: ALg8bN7j5uyBD7LMkFHElKSmB2WzV8k9UnIDZzmF+Pyq/6/q1SV9ca3mw5PacKN4LihYjwZi0ab1 X-Received: by 2002:a62:4156:: with SMTP id o83mr32488473pfa.72.1548892473805; Wed, 30 Jan 2019 15:54:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548892473; cv=none; d=google.com; s=arc-20160816; b=H40TLXSZwtD83W00Aiu4tmWN1l0Rl64onTLvxEKzVvnw8YYkBc/zZB1bFbgD3RaRDa vN4ddmavBrIKPixPj5d/WF8sxst6xpC909kdRwRlZZ+/F5EVsx98tiFegxcQSSAhoH1K kMGfYlWQ3RUjV5IjhbRoX2HVq3NaAMeLqn7ME7OFnKPAc/mT5ifbmmZqXbwOBpmf5+4b mIu8C4ZEBFDKc6VpsAFViTn11S9HJkCUsV9mqepdsLvfzh6Qb/3dPoCLOQHADv5M2Bio E0QREY/QtGXYmNO+jMXNdjMJm5edUuHp88MGVRBQvCyj1PcY8xNtiSxds3axCADFtCqn +ztw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=yHTmlSdsw0ddv0WZw6NQBaf+Lx/v0lncj03Huj6mH3Y=; b=wG+9tI9WC2bPefhPc6vXVWiLyDTLo9gs+1t939D8498CD1BKBYs5liycfSpq4UoaVA Vm4C3O7Uq05ibZEYIArcZ5xAhVsV0DfFoY6ar4ih2KJu8lZaFllZNcdlqAkeiRsr8HmT kIa/XbHtogqcKvF4pSN0GVLbdbTArvc/1REmoajjvPVEkibVltvUImapqiD2aupeGHO0 dWdL++MLpSVTLCervW1B/+GgCdWGmTUyr6Jw/m0ShL6tykcLcwF4yMWqmLs5qycFWSAl 2hrf00EKrFOAgpoaY/AX+5L8RSTZQ5ObhU4dhKhU3jlqRarH55XvV7x6SRVoL0dMwoaa 8AFg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=bK4TeC23; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 66si2877228plc.125.2019.01.30.15.54.18; Wed, 30 Jan 2019 15:54:33 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=bK4TeC23; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727111AbfA3Xx0 (ORCPT + 99 others); Wed, 30 Jan 2019 18:53:26 -0500 Received: from mail-qt1-f182.google.com ([209.85.160.182]:44375 "EHLO mail-qt1-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726233AbfA3Xx0 (ORCPT ); Wed, 30 Jan 2019 18:53:26 -0500 Received: by mail-qt1-f182.google.com with SMTP id n32so1587041qte.11 for ; Wed, 30 Jan 2019 15:53:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yHTmlSdsw0ddv0WZw6NQBaf+Lx/v0lncj03Huj6mH3Y=; b=bK4TeC23YsjsP8RNdRKPxHm1ViwVEHRD6VQtzGDNTmcZTErjiXAPaCF5azuC4F2rkC kYLbhBtHWvyDyAhDY02uEB6Zpw0kjXIHiTDSjqNitSW3exLUEtHNV8gbs0pZ8CKknGlZ cBx50IZSB3mHYo/gce5rIAlWQVq1cE0SY7EyXWosrf+7BS4DXcnGNYpi+6YaFAa7UFBY 2Z+9okFNtpOOcvWqOz68sRKeuvbMx0oHNhcUgZOu8+y1pfuWnYRQzJblcGGGY8XokKS0 aRe/2cK9DvDfKzFucfkjVYhv0reC1415nsQagi5tHgpJwt1Fs1Ovl4u3qXdQeNTvjtZt S7VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yHTmlSdsw0ddv0WZw6NQBaf+Lx/v0lncj03Huj6mH3Y=; b=ignxDNLyIKn3W00sHxCUURYipSMTvtiA3shXXUgpiUII4PpcNajxlAwNJPtwasR7VE WGop+36I+7SiD/S3yoAzBcPKk+Kjl1/r2y7vMfXRnKV2Qe7DHq69QV2gnlhCWvKTrRFY 0CF77YuWrwD6NhSVjNoV5A1ylz0+y8P9CeJTXWvYDNTwQB98RIgkYQFnCVgLOHJGhwRL WhL4j8xow78zQb6QMEaA36N1IK7OU4nYgozhxDcs1FnTljPFrh7Dii55BeA49Jt1jJcE vGWKq+Y2NgSYRojlZ6iooJKm+qa9lpYddicgP1FS/upRT247I9wdsCk/UL5M1ewRh8ua umEw== X-Gm-Message-State: AJcUukfNtuxjJqKRhQwrPlqceqUK7Bnk4RBUf7KYB+A90w5cONL2AfWw rgt0gRZaSZA0/rKfiHFH4lv0soLix8KuMy/aoa8+Rg== X-Received: by 2002:a0c:d29b:: with SMTP id q27mr30512882qvh.62.1548892405083; Wed, 30 Jan 2019 15:53:25 -0800 (PST) MIME-Version: 1.0 References: <20190130174847.GD18811@dhcp22.suse.cz> In-Reply-To: <20190130174847.GD18811@dhcp22.suse.cz> From: Yang Shi Date: Wed, 30 Jan 2019 15:53:13 -0800 Message-ID: Subject: Re: [LSF/MM TOPIC] memory reclaim with NUMA rebalancing To: Michal Hocko Cc: lsf-pc@lists.linux-foundation.org, Linux MM , LKML , linux-nvme@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jan 30, 2019 at 9:48 AM Michal Hocko wrote: > > Hi, > I would like to propose the following topic for the MM track. Different > group of people would like to use NVIDMMs as a low cost & slower memory > which is presented to the system as a NUMA node. We do have a NUMA API > but it doesn't really fit to "balance the memory between nodes" needs. > People would like to have hot pages in the regular RAM while cold pages > might be at lower speed NUMA nodes. We do have NUMA balancing for > promotion path but there is notIhing for the other direction. Can we > start considering memory reclaim to move pages to more distant and idle > NUMA nodes rather than reclaim them? There are certainly details that > will get quite complicated but I guess it is time to start discussing > this at least. I would be interested in this topic too. We (Alibaba) do have some usecases with using NVDIMM as NUMA node. The node balancing (or cold/hot data migration) is one of our needs to achieve optimal performance for some workloads. I also proposed a related topic. Regards, Yang > -- > Michal Hocko > SUSE Labs >