Received: by 2002:a05:7412:b795:b0:e2:908c:2ebd with SMTP id iv21csp175187rdb; Wed, 1 Nov 2023 23:14:16 -0700 (PDT) X-Google-Smtp-Source: AGHT+IEIWJIhyMU3EViJJbPdR1bgXao+80nzZ9sd20JIYEjqScw97KSLL+JNz9v+zEFtxvZ1QoCd X-Received: by 2002:a05:6a20:8421:b0:181:16c7:6cd0 with SMTP id c33-20020a056a20842100b0018116c76cd0mr6364195pzd.17.1698905655715; Wed, 01 Nov 2023 23:14:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1698905655; cv=none; d=google.com; s=arc-20160816; b=QS1NwU37zmxVnd/1fvnnYGC0NFzCr/FTyi8Kxdab7fRiuggeLKS7x/GIM+7AElqC9+ l/zbXHJlnRAL98ICEa9qWjsR1fKcAfoA95hn397p9ICQ0jz2scwI3tDZNVkz1W8/pFhL OFkMlrQgDFcsLyfNYHPaWtz4zR3noEuCorKU1dgMbp47zco1cgJnugpHTTmfuuAbIs/q OQl3Ue35iw5qaG1+SPuSCEgPgAtPywAJWFzyJxh2P+cvGsKeMVk2kblAWQd0E6Xmpggy 0Bw7pGUmOlzmfOqIGVVuhBrJ991TqmHgZ9Lrm5GSKvwRZQvcctGp5rCnjIfaXJ9oB0eS un1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:dkim-signature; bh=bLC8jJh8l+GUMS1zebfv+JM9TqUrK5YLnFTrvezd+MQ=; fh=If5si61B8QOa0J51dxCB8FjB0+xTyvQIzAj+VYhM/eo=; b=ucUI6ZolahRqaAE6T/Qy1yMcYyVNNgxY2F095/rKRN1fHyQXaNHySnNZQmUpH1awWt 1CngeyssitiV5Nk6JZxfyuZJLFAMbROOpVNqbeZOb++60csMtgza+HfnaMKIvMf3ORP0 46SfETAKQseaU9fa66fE4h8nE3AruSFaLZHAQ/8dc30L28s/0u3yF8Fhau70H3Cf4dcC DWyFACY3rsSuR9ZDo2/Phw2zN8SoFcBZici06tS/M2h7SWjLjy04bukiS5G2oTCRWoJL FL18kIr39RNCtdYjhFm6Qp4zFNSve//DTA+QJy37h2ZGLZDpxrlQ6P7SitMMnOrOdsOC 2AxQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TdR+59P2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from fry.vger.email (fry.vger.email. [2620:137:e000::3:8]) by mx.google.com with ESMTPS id k13-20020a170902f28d00b001cc3473657bsi4293342plc.215.2023.11.01.23.14.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Nov 2023 23:14:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=TdR+59P2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by fry.vger.email (Postfix) with ESMTP id E880881C0C89; Wed, 1 Nov 2023 23:14:10 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at fry.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231673AbjKBGNW (ORCPT + 99 others); Thu, 2 Nov 2023 02:13:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55278 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229445AbjKBGNV (ORCPT ); Thu, 2 Nov 2023 02:13:21 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B0B5DB; Wed, 1 Nov 2023 23:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1698905595; x=1730441595; h=from:to:cc:subject:in-reply-to:references:date: message-id:mime-version; bh=/i1nfGSh8lqsODaI9yo1bI1rYHQ0A82xnF/8KFBEOuc=; b=TdR+59P2Yivda+0YH6r80VDP582r4Ev5KAEF/Bedd0AFozTN8k/biKc2 QUOFgCbiRFIKt4BxBzxricDVHPDYMLLn83boUSPk8JI1fa8Q7YffegajK hYPu0zHcDLXlJRfY71zOnB6H+lGtFNP6/Ns/81B5L583TJY3ZkUQ4m7fe szvKQs04MCyYhEbGp3twejwLPWQyoRzmj92ewAvKmPprMVJXRwUR2v/W1 jnXLfhBBhynb3eM2BrOaHhJRSgFz4LyCwkBV41dQm5n3lMmoZnN3feH51 bGY9cHv9asKPbnuGm05VRS3Jd2kv032yQLn7mj0nsmmYKMAupW70n6V9r g==; X-IronPort-AV: E=McAfee;i="6600,9927,10881"; a="368852981" X-IronPort-AV: E=Sophos;i="6.03,270,1694761200"; d="scan'208";a="368852981" Received: from orviesa002.jf.intel.com ([10.64.159.142]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Nov 2023 23:13:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.03,270,1694761200"; d="scan'208";a="2329842" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.238.208.55]) by orviesa002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Nov 2023 23:13:11 -0700 From: "Huang, Ying" To: Michal Hocko Cc: Johannes Weiner , Gregory Price , linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, aneesh.kumar@linux.ibm.com, weixugc@google.com, apopple@nvidia.com, tim.c.chen@intel.com, dave.hansen@intel.com, shy828301@gmail.com, gregkh@linuxfoundation.org, rafael@kernel.org, Gregory Price Subject: Re: [RFC PATCH v3 0/4] Node Weights and Weighted Interleave In-Reply-To: (Michal Hocko's message of "Wed, 1 Nov 2023 15:01:22 +0100") References: <20231031003810.4532-1-gregory.price@memverge.com> <20231031152142.GA3029315@cmpxchg.org> <87msvy6wn8.fsf@yhuang6-desk2.ccr.corp.intel.com> Date: Thu, 02 Nov 2023 14:11:09 +0800 Message-ID: <87il6k1y82.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Spam-Status: No, score=-1.3 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on fry.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (fry.vger.email [0.0.0.0]); Wed, 01 Nov 2023 23:14:11 -0700 (PDT) Michal Hocko writes: > On Wed 01-11-23 10:21:47, Huang, Ying wrote: >> Michal Hocko writes: > [...] >> > Well, I am not convinced about that TBH. Sure it is probably a good fit >> > for this specific CXL usecase but it just doesn't fit into many others I >> > can think of - e.g. proportional use of those tiers based on the >> > workload - you get what you pay for. >> >> For "pay", per my understanding, we need some cgroup based >> per-memory-tier (or per-node) usage limit. The following patchset is >> the first step for that. >> >> https://lore.kernel.org/linux-mm/cover.1655242024.git.tim.c.chen@linux.intel.com/ > > Why do we need a sysfs interface if there are plans for cgroup API? They are for different target. The cgroup API proposed here is to constrain the DRAM usage in a system with DRAM and CXL memory. The less you pay, the less DRAM and more CXL memory you use. -- Best Regards, Huang, Ying