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 1881FC433EF for ; Thu, 2 Jun 2022 06:43:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231357AbiFBGnv (ORCPT ); Thu, 2 Jun 2022 02:43:51 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45552 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231219AbiFBGns (ORCPT ); Thu, 2 Jun 2022 02:43:48 -0400 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94DFADF7A for ; Wed, 1 Jun 2022 23:43:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654152226; x=1685688226; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=KUS8mVgdTc5Hj0xMVFCoSGE47Yrh0WZN2tGJ3zjuvKw=; b=cdga+2IJg81u6D5Zx6HQhOTz3NYEY3s2/eobr7pmK9w9D3bY4xZp9dUp E0W+sKmSXR2ihkkqYYCO/VH2v6T2AB+4F16gLrtONv8CKKC02cCXbscOm JGotsms/nOlrFZ90z81s2WkyRrWppkEIvpYwDwWl1tsXROgKE1B0F8kO0 dKAPuvq06yCiso9i7svownivtJSrdvcvEam91zvB1mOdTtomi/Ns4ly8P 8ENwUhJOZXwmWQ+v267ZnAFAsUkRqCNhosfGpJ3SbaQvq3ouTqC+r+3TK Ibe2etcMLuDDWx7VKvhtUYatLsmyoByFYcRsngPihrqLYZ1fC5LwGFCvc Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10365"; a="275570229" X-IronPort-AV: E=Sophos;i="5.91,270,1647327600"; d="scan'208";a="275570229" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jun 2022 23:43:46 -0700 X-IronPort-AV: E=Sophos;i="5.91,270,1647327600"; d="scan'208";a="606683307" Received: from yanqingl-mobl1.ccr.corp.intel.com ([10.254.212.10]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Jun 2022 23:43:41 -0700 Message-ID: <2316b2f571cd812b5c2e4335c2ed51a227005098.camel@intel.com> Subject: Re: [RFC PATCH v4 6/7] mm/demotion: Add support for removing node from demotion memory tiers From: Ying Huang To: "Aneesh Kumar K.V" , linux-mm@kvack.org, akpm@linux-foundation.org Cc: 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: Thu, 02 Jun 2022 14:43:38 +0800 In-Reply-To: <20220527122528.129445-7-aneesh.kumar@linux.ibm.com> References: <20220527122528.129445-1-aneesh.kumar@linux.ibm.com> <20220527122528.129445-7-aneesh.kumar@linux.ibm.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2022-05-27 at 17:55 +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. > > 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# Why do you need this? Do you have some real users? Best Regards, Huang, Ying [snip]