Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3251244yba; Tue, 16 Apr 2019 07:41:13 -0700 (PDT) X-Google-Smtp-Source: APXvYqxMfCl/BX+SLtEbjuDMuBnJKd1PzL3ubmNRFM8/v9zG1NhQX1UdO+kjG7KKHh73rDSdjzhv X-Received: by 2002:a17:902:3e5:: with SMTP id d92mr78896106pld.11.1555425673147; Tue, 16 Apr 2019 07:41:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555425673; cv=none; d=google.com; s=arc-20160816; b=qQgC0HskJzhA5iZUOpHTl8NRHp9T+3E6k1PFTTSMi5x/K0nKhUmkOL3l9TWwYh7dvw G1vu4UTC8wqT8RZIP7hVepYm3XUkIKuVyoOxFMTS/bI9KzmBB2+vO1qTNJrs1eq2s2zm h/dJdOfM/w9xRZjzHsoNIc8Ns9E9Vh6QL4BORtmFL6BGH9xUw25xtTGNsBEt9bLE56RY vwRFKtRgl9/gQsRTFSVZwAqyYf4u31roEmSQH+lau4K0WSb0dqvn2DXCaxxCAwgC5lII Qy8MnwOyKOJtt88HaZm3u+k5bSqJSN0eoK53y4A2gJwMGyOc1nm8oZlFd1nhltkGkUf2 gPNQ== 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=kE2sK5B8RVXnzpG429UFSw1OEJu2pJbwFBiyEfcLI+A=; b=sXTUKnzADJ79mg2oC6EI+flt59LhNu7iaofrqjYv8D1KzSoizPOxZwF1VfuPY8pr39 8vHDN/j4OahytAXoF2Y5B+6aQkEmZPWyFguDdWyN7abtC2pDExkGQg7T9TmgxbHxntxx cOeg0t+4lOQ/qernZ2d3FseDk5t8OFnaooyqCcgprrAYCoc71WfrBORwx0Kvdp8mZWMh W76JqHJhnYC8PsdJrQrrrHDfGSzzvWr3cO0vWYcVVetTiF1cqgOJPQNDKrFsXnREuf4T 8PQPlsNhq8puQ6ywFhbAL+Zi6gDje5wec8qyMLhE+liDbr+jnbIEVpC4SVy1Jce6OgzD V1PQ== 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p17si48582253pgl.181.2019.04.16.07.40.56; Tue, 16 Apr 2019 07:41:13 -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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729582AbfDPOkB (ORCPT + 99 others); Tue, 16 Apr 2019 10:40:01 -0400 Received: from mx2.suse.de ([195.135.220.15]:39840 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726605AbfDPOkB (ORCPT ); Tue, 16 Apr 2019 10:40:01 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 366E2AE56; Tue, 16 Apr 2019 14:40:00 +0000 (UTC) Date: Tue, 16 Apr 2019 16:39:58 +0200 From: Michal Hocko To: Dave Hansen Cc: Yang Shi , mgorman@techsingularity.net, riel@surriel.com, hannes@cmpxchg.org, akpm@linux-foundation.org, keith.busch@intel.com, 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: <20190416143958.GI11561@dhcp22.suse.cz> References: <1554955019-29472-1-git-send-email-yang.shi@linux.alibaba.com> <20190412084702.GD13373@dhcp22.suse.cz> <20190416074714.GD11561@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 16-04-19 07:30:20, Dave Hansen wrote: > On 4/16/19 12:47 AM, Michal Hocko wrote: > > You definitely have to follow policy. You cannot demote to a node which > > is outside of the cpuset/mempolicy because you are breaking contract > > expected by the userspace. That implies doing a rmap walk. > > What *is* the contract with userspace, anyway? :) > > Obviously, the preferred policy doesn't have any strict contract. > > The strict binding has a bit more of a contract, but it doesn't prevent > swapping. Yes, but swapping is not a problem for using binding for memory partitioning. > Strict binding also doesn't keep another app from moving the > memory. I would consider that a bug. -- Michal Hocko SUSE Labs