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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6A2ADCCA48A for ; Wed, 8 Jun 2022 02:03:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1392491AbiFHB6O (ORCPT ); Tue, 7 Jun 2022 21:58:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49312 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1588736AbiFGXzA (ORCPT ); Tue, 7 Jun 2022 19:55:00 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D68FF18219D for ; Tue, 7 Jun 2022 16:40:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654645202; x=1686181202; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=ZjlOk8azHhDHFFrQPq91H0uTrw45sF8jDpP42SnJxhM=; b=lr1Tn8qWMU9rVd+Y42dc5t+H5lKvlNeyVICMqarzwZPpO2UNVIhtPXCi 79zW43Whu5c7soS3d9uBslqzX64TLAfYwKJnKg4WWWR2WIp/DKtl8pSGA azDKKYjZR+kcgMMSiSUdv7HPfqD97oLuzYn7t2pwmos6PWHe2GxU/+wja ltnqALFa0wgpRpicPVlr5Xug4sEnd+ijXl1iiMTREyMPV3+8qQfnAk/tP VPSBfk6UY6sNdXayCJ6sqMbIxeD4appM4N48SevpqhzEEq2xAz9GY1JS7 ZD3HH0ftbPv0w9XMUFjdZl7RhuVyIR9jTgNdazUP22hn1ZU6ZrsMOZ9uC A==; X-IronPort-AV: E=McAfee;i="6400,9594,10371"; a="276801993" X-IronPort-AV: E=Sophos;i="5.91,284,1647327600"; d="scan'208";a="276801993" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jun 2022 16:40:01 -0700 X-IronPort-AV: E=Sophos;i="5.91,284,1647327600"; d="scan'208";a="579810172" Received: from schen9-mobl.amr.corp.intel.com ([10.251.8.166]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jun 2022 16:40:01 -0700 Message-ID: <0c2fac38720710aebe2b667807c647e8a5aa5441.camel@linux.intel.com> Subject: Re: [PATCH v5 6/9] mm/demotion: Add support for removing node from demotion memory tiers From: Tim Chen To: "Aneesh Kumar K.V" , linux-mm@kvack.org, akpm@linux-foundation.org Cc: Wei Xu , Huang Ying , Greg Thelen , Yang Shi , Davidlohr Bueso , Tim C Chen , Brice Goglin , Michal Hocko , Linux Kernel Mailing List , Hesham Almatary , Dave Hansen , Jonathan Cameron , Alistair Popple , Dan Williams , Feng Tang , Jagdish Gediya , Baolin Wang , David Rientjes Date: Tue, 07 Jun 2022 16:40:00 -0700 In-Reply-To: <20220603134237.131362-7-aneesh.kumar@linux.ibm.com> References: <20220603134237.131362-1-aneesh.kumar@linux.ibm.com> <20220603134237.131362-7-aneesh.kumar@linux.ibm.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2022-06-03 at 19:12 +0530, Aneesh Kumar K.V wrote: > This patch adds the special string "none" as a supported memtier value > that we can use to remove a specific node from being using as demotion target. And also such node will not participate in promotion. That is, hot memory in it will not be promoted to other nodes. > > For ex: > :/sys/devices/system/node/node1# cat memtier > 1 > :/sys/devices/system/node/node1# cat ../../memtier/memtier1/nodelist > 1-3 > :/sys/devices/system/node/node1# echo none > memtier > :/sys/devices/system/node/node1# > :/sys/devices/system/node/node1# cat memtier > :/sys/devices/system/node/node1# cat ../../memtier/memtier1/nodelist > 2-3 > :/sys/devices/system/node/node1# > >