Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp2067522rwi; Fri, 28 Oct 2022 02:35:43 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7HlY8VfhN6/4vQZbCr/VFKVyIW0XvmnPA3aBDsBRvX3WRYauwrwiZVjkXU4msq/swLyHeG X-Received: by 2002:a17:902:d3c6:b0:186:f22a:66e with SMTP id w6-20020a170902d3c600b00186f22a066emr5446931plb.154.1666949742776; Fri, 28 Oct 2022 02:35:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666949742; cv=none; d=google.com; s=arc-20160816; b=Up4QhbdEp8NEub5oI9ZAAWwVjW3Bf+RynwJk9iLKxf9MWGKZp5MI0U1NFVtjnZLJsZ eIGXWesht3SguzbwP58rPsBYUDlzrMm1+5AXe20KTytxCA1Bfq8cOS3B4ADUcMemPwlj av9/7dQths8TdBXSNgYCdXW3G/kJpXcxsD7gFdFyQP1t0g+SQV/OEPeRQyScL/kVunxR B9yIe0yKu3CMJ7z+UU7r+L0ubtdOWm+XC5iGllJup9oOzuDkxxd7+wHzQZ2rE9VVv9tO rYzui4Fs/glUY37jXXOoM2rMjKULnTTRZW9t8mWQ7qYEhI0Jcr36FEwjnenyBJMYAWeU Ib0A== 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:in-reply-to :date:references:subject:cc:to:from:dkim-signature; bh=QKrBbY/bW6eKL14DjqWx1J+MBCbzq9RxDmsO4zfWh5o=; b=J+tH9zEMe5M9E+2gae93QRM5qhRVR2MG1zVPTAz9fXcXtYXqplDGvAmqp0jzd7X2gV KFmJhmRwxGaT19rKUnRfVky47M7TTe3eX9g1FWAfhck74nw9Sw7ZLiKlq2vETmDEDjgO oya69vaG5IWbWOFf6klYcFNnVFycsfBQQxmKs0SSQPFOKZsTOFh+kJOektHDrJQQ0NIg oSY2F5Yxrq1s2uckvUSo6UNKTMyka7VzH1u+hZ7iuzsYTWzwJZaesQjJ4PLMYytZKeZO QvCQknrRcJWkR6Ot90VCtMqxMkEuxEN4zvQ/g3FlZJ29B36WEL2yrKyNVtSSEtjf31z/ XFNw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="KQRhi/nI"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bi11-20020a170902bf0b00b001727963f929si312683plb.130.2022.10.28.02.35.31; Fri, 28 Oct 2022 02:35:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="KQRhi/nI"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229920AbiJ1Ieq (ORCPT + 99 others); Fri, 28 Oct 2022 04:34:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33798 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229629AbiJ1Ien (ORCPT ); Fri, 28 Oct 2022 04:34:43 -0400 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 861EB1C42D for ; Fri, 28 Oct 2022 01:34:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1666946082; x=1698482082; h=from:to:cc:subject:references:date:in-reply-to: message-id:mime-version; bh=I7+l1li97AG1W4nCdyskwIa37THe0xzjljy5/l3afeQ=; b=KQRhi/nIPXbyx53oWRDRqu2cA9MhLAeG0TQrztfQ6uyb6ItQ1zSs/lLC 4YI/UkxHBHGuM2VXpxE1h7uqs6oPKNpCBYBDb24T3j6TejBUnsEAnAXR4 2ZCGmOShB3ZZfcljjPTW/+hNPlRb7lBrn5s7FToQErET+iaO1S7H5ELe3 OvMvgYtTmXwo3uOlXFErMDJYuHv6QerA76VOL7nj1KZP+3k/FAD15IPCD GG21PPh5yIiMiqO2YknRAzZMG1Hekl1bpS8AeVR+8RK7Azh1SB0sh0Pcl 7erpAHPqcebpFmiCkvmYt5jrLOoeQGJCPv1QMsMejY2carzpYhe2U2lkH Q==; X-IronPort-AV: E=McAfee;i="6500,9779,10513"; a="335083761" X-IronPort-AV: E=Sophos;i="5.95,220,1661842800"; d="scan'208";a="335083761" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2022 01:34:41 -0700 X-IronPort-AV: E=McAfee;i="6500,9779,10513"; a="632708139" X-IronPort-AV: E=Sophos;i="5.95,220,1661842800"; d="scan'208";a="632708139" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.238.208.55]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Oct 2022 01:34:37 -0700 From: "Huang, Ying" To: Bharata B Rao Cc: Aneesh Kumar K V , , , Andrew Morton , Alistair Popple , "Dan Williams" , Dave Hansen , Davidlohr Bueso , Hesham Almatary , Jagdish Gediya , Johannes Weiner , Jonathan Cameron , Michal Hocko , Tim Chen , Wei Xu , Yang Shi Subject: Re: [RFC] memory tiering: use small chunk size and more tiers References: <20221027065925.476955-1-ying.huang@intel.com> <578c9b89-10eb-1e23-8868-cdd6685d8d4e@linux.ibm.com> <877d0kk5uf.fsf@yhuang6-desk2.ccr.corp.intel.com> <59291b98-6907-0acf-df11-6d87681027cc@linux.ibm.com> <8735b8jy9k.fsf@yhuang6-desk2.ccr.corp.intel.com> <0d938c9f-c810-b10a-e489-c2b312475c52@amd.com> Date: Fri, 28 Oct 2022 16:33:48 +0800 In-Reply-To: <0d938c9f-c810-b10a-e489-c2b312475c52@amd.com> (Bharata B. Rao's message of "Fri, 28 Oct 2022 13:34:46 +0530") Message-ID: <87tu3oibyr.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Spam-Status: No, score=-7.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bharata B Rao writes: > On 10/28/2022 11:16 AM, Huang, Ying wrote: >> If my understanding were correct, you think the latency / bandwidth of >> these NUMA nodes will near each other, but may be different. >> >> Even if the latency / bandwidth of these NUMA nodes isn't exactly same, >> we should deal with that in memory types instead of memory tiers. >> There's only one abstract distance for each memory type. >> >> So, I still believe we will not have many memory tiers with my proposal. >> >> I don't care too much about the exact number, but want to discuss some >> general design choice, >> >> a) Avoid to group multiple memory types into one memory tier by default >> at most times. > > Do you expect the abstract distances of two different types to be > close enough in real life (like you showed in your example with > CXL - 5000 and PMEM - 5100) that they will get assigned into same tier > most times? > > Are you foreseeing that abstract distance that get mapped by sources > like HMAT would run into this issue? Only if we set abstract distance chunk size large. So, I think that it's better to set chunk size as small as possible to avoid potential issue. What is the downside to set the chunk size small? Best Regards, Huang, Ying