Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp4307751yba; Wed, 17 Apr 2019 08:49:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqwc87OaFbXE1Imf1QOfusDDOCZDuBUycpmdEU6E/IXKmE9pHTGwwQSuhalO8gUejc/MudUC X-Received: by 2002:a17:902:1105:: with SMTP id d5mr66530966pla.311.1555516159878; Wed, 17 Apr 2019 08:49:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555516159; cv=none; d=google.com; s=arc-20160816; b=jJAZyKd8D1MxexhN8torWHsjqpYS9vdEsPPCMT6vOOItYLRvafWyBhV2LK2m9+ewNd cPPPMH4I3lFFCB+m4cnObgBYHylp1ZJL+wcpsomXvm+s5i7t1nGkMgMp6tH+GYJfB8mX /rZyhXnQQcZMGNdPAnKjqxggyD4WDqA+APtE6pBXVw/HD9ZqyTHpUS+GhyFq/QR2aMfp TS2sSq4Da76zsa3TtCx0huwJETRxm3w69fpV5nkVGJ/ZbYtSvmUdJsO0sWvMw+ufcnRL T7f2R28otAbOcyuUZK2w4fmRS1YOX3zpjtmmK1tpK102ln5j8ahegkO8e6IOb5TzZdLe VvCw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=1tzss/eTAlkwslHVAdew1DA7WfJBCr7rAadPs81a+mw=; b=WDzcmdZq5HRyrOAQiaFlvM+ylFXTYCdnCqzCNvZiGi/KM2DrBdR485UZyq/yKXI+Dx 0sV1N5vSw/MRdB9A1INKiJLO1dA8Oxkx7nCgQKa88jtJa+ogstnbITWA0DkSrUKIcQ9H bUt/sl/9sD14ANQbXpu/u2UnEPTIBjwjj+z5SLnJqveKk3t0AvPhlnwt4Fc5/WRNUTNC q+przsVnRtWta5LCuh1SzLVGfwxHvmxXvAWxlJC1+7/hAziZGMU1lyQIkIfXSqHPhYDn nCy9Xz5FRGC49BO6t2sCvEpjSQvc8OpZXweG+/5c1SiuaMSJVg9VddFx9+Ese8347Ri6 vrDQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1si26727907plu.320.2019.04.17.08.49.04; Wed, 17 Apr 2019 08:49:19 -0700 (PDT) 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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732792AbfDQPrW (ORCPT + 99 others); Wed, 17 Apr 2019 11:47:22 -0400 Received: from mga12.intel.com ([192.55.52.136]:61296 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732476AbfDQPrW (ORCPT ); Wed, 17 Apr 2019 11:47:22 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Apr 2019 08:43:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,362,1549958400"; d="scan'208";a="162731832" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by fmsmga004.fm.intel.com with ESMTP; 17 Apr 2019 08:43:54 -0700 Date: Wed, 17 Apr 2019 09:37:39 -0600 From: Keith Busch To: Michal Hocko Cc: Dave Hansen , Yang Shi , mgorman@techsingularity.net, riel@surriel.com, hannes@cmpxchg.org, akpm@linux-foundation.org, dan.j.williams@intel.com, fengguang.wu@intel.com, fan.du@intel.com, ying.huang@intel.com, ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [v2 RFC PATCH 0/9] Another Approach to Use PMEM as NUMA Node Message-ID: <20190417153739.GD4786@localhost.localdomain> References: <1554955019-29472-1-git-send-email-yang.shi@linux.alibaba.com> <20190412084702.GD13373@dhcp22.suse.cz> <20190416074714.GD11561@dhcp22.suse.cz> <876768ad-a63a-99c3-59de-458403f008c4@linux.alibaba.com> <20190417092318.GG655@dhcp22.suse.cz> <20190417152345.GB4786@localhost.localdomain> <20190417153923.GO5878@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190417153923.GO5878@dhcp22.suse.cz> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 17, 2019 at 05:39:23PM +0200, Michal Hocko wrote: > On Wed 17-04-19 09:23:46, Keith Busch wrote: > > On Wed, Apr 17, 2019 at 11:23:18AM +0200, Michal Hocko wrote: > > > On Tue 16-04-19 14:22:33, Dave Hansen wrote: > > > > Keith Busch had a set of patches to let you specify the demotion order > > > > via sysfs for fun. The rules we came up with were: > > > > > > I am not a fan of any sysfs "fun" > > > > I'm hung up on the user facing interface, but there should be some way a > > user decides if a memory node is or is not a migrate target, right? > > Why? Or to put it differently, why do we have to start with a user > interface at this stage when we actually barely have any real usecases > out there? The use case is an alternative to swap, right? The user has to decide which storage is the swap target, so operating in the same spirit.