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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id B3975C19F29 for ; Thu, 28 Jul 2022 17:23:12 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E602D8E0002; Thu, 28 Jul 2022 13:23:11 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E0FDE8E0001; Thu, 28 Jul 2022 13:23:11 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CD8B48E0002; Thu, 28 Jul 2022 13:23:11 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id BE1578E0001 for ; Thu, 28 Jul 2022 13:23:11 -0400 (EDT) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 8D9AB81519 for ; Thu, 28 Jul 2022 17:23:11 +0000 (UTC) X-FDA: 79737179382.09.593B683 Received: from mail-qk1-f170.google.com (mail-qk1-f170.google.com [209.85.222.170]) by imf04.hostedemail.com (Postfix) with ESMTP id E283E400AE for ; Thu, 28 Jul 2022 17:23:10 +0000 (UTC) Received: by mail-qk1-f170.google.com with SMTP id c3so1931157qko.1 for ; Thu, 28 Jul 2022 10:23:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpxchg-org.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=1bpeiU6xJe06BhKMBB9TymWuJgsApmhu1bP3WtUTIhI=; b=pQcHZGMM8cnpt7ARDuITkHvi77Yt5Zt5QtdeTeHfFp1ZXshN1/OlmE/QHCwGn9LiIC TtiCHmD6pv/6lfByvazNLBF4GtYkQGjX0sMu+GEMqTFSfDamNZ3kMGX+Nh6jQWBop6j5 2qD6m+i9xkBSz86mC5pO/wAHYUtokUDqri3o2wud2JOURD/8DV2iUQWhHHtarF0HKoBI OXA/5yWUmtmnJMVF7M41H+zE15BzHpbvvaXD4h0o793q9zohrw9gY9Z+BFJldGP7cOlK ExO1s68ZGans3vqRusMj01Q8/dvfO7afHB6GRi3UNq7dxRgwm1mkfqpst8w1OZEbefOJ GIyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=1bpeiU6xJe06BhKMBB9TymWuJgsApmhu1bP3WtUTIhI=; b=rHzgFkpyKV4GmIZvnk/zjIZ1Vbu0NK7dy8HlfknijqUEXi/0MF/f37GKtmwvUPEvEn jvXZ/QaSLBRWcH4957dAOTLoNe6GDdI7M7ppXgO+sOqBR5ZzNkbCc2pv8Cdfq3wME8M8 Q9WORQqU1v6DQUuHVZ+obJ0/0CGN82ojppY0iOSw4PseAnxVvAxNRqoUca+uutozwidJ qdp4dDXvyDpMFXYcywy2Gz8a7KB/qy58juZeAJ0S32hlAKcmMDr4kIA8Yc7mBVju+KJ2 f/KKDBVO7DhAb/JUpZCMCTFrblIfnPEuWdoY2Z2P/63nKDfB0tGiU7LRPSyVPpNX65QO RGdg== X-Gm-Message-State: AJIora+7uAp7B/mgwlVXk+WsmuaFgd9SCl/VO2jlNVSfaIgvKcKIqK+Y 5GLl13hqIvDUu0c9fRsnpnpKYQ== X-Google-Smtp-Source: AGRyM1uOeNQ6O5O6VgA66Jbex+hGdMpMLlFOcjsQPWG4mNYu3adiReX5u8cPXRh948v4hzR2Ui1l/g== X-Received: by 2002:a05:620a:44d4:b0:6b6:229e:dc5b with SMTP id y20-20020a05620a44d400b006b6229edc5bmr20148181qkp.327.1659028990091; Thu, 28 Jul 2022 10:23:10 -0700 (PDT) Received: from localhost ([2620:10d:c091:480::1:994f]) by smtp.gmail.com with ESMTPSA id t7-20020a375f07000000b006af50b6f10csm876959qkb.61.2022.07.28.10.23.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 28 Jul 2022 10:23:09 -0700 (PDT) Date: Thu, 28 Jul 2022 13:23:08 -0400 From: Johannes Weiner To: "Huang, Ying" Cc: Aneesh Kumar K V , Wei Xu , linux-mm@kvack.org, akpm@linux-foundation.org, Yang Shi , Davidlohr Bueso , Tim C Chen , Michal Hocko , Linux Kernel Mailing List , Hesham Almatary , Dave Hansen , Jonathan Cameron , Alistair Popple , Dan Williams , jvgediya.oss@gmail.com, Jagdish Gediya Subject: Re: [PATCH v10 1/8] mm/demotion: Add support for explicit memory tiers Message-ID: References: <20220720025920.1373558-1-aneesh.kumar@linux.ibm.com> <20220720025920.1373558-2-aneesh.kumar@linux.ibm.com> <87k080wmvb.fsf@yhuang6-desk2.ccr.corp.intel.com> <9e9ba2e4-3a87-3a79-e336-8849dad4856a@linux.ibm.com> <87lesfuzhj.fsf@yhuang6-desk2.ccr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lesfuzhj.fsf@yhuang6-desk2.ccr.corp.intel.com> ARC-Authentication-Results: i=1; imf04.hostedemail.com; dkim=pass header.d=cmpxchg-org.20210112.gappssmtp.com header.s=20210112 header.b=pQcHZGMM; spf=pass (imf04.hostedemail.com: domain of hannes@cmpxchg.org designates 209.85.222.170 as permitted sender) smtp.mailfrom=hannes@cmpxchg.org; dmarc=pass (policy=none) header.from=cmpxchg.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1659028991; a=rsa-sha256; cv=none; b=Y4T2ZZvXOICoHJL8Y5W/Xlh0bVfHDIuCxBvhkifN7VJwXF2sxMYvFoZP4yFn866whE2aRm Idxc2vICeW6LdaBpIsx21aHralYaN/aGv0iJKWzupqfoTJdu7uZ9hbs1I1bzvvyI/psNeq Vnmofr3gvTAgTea+7bhS2YB7g2g5kiA= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1659028991; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=1bpeiU6xJe06BhKMBB9TymWuJgsApmhu1bP3WtUTIhI=; b=rotToRGc1N5dSZI7vVHcK6+DKZMrAeKoAiLm0XwyyDeQ3bb2NQbANN/4b3F15QwWVu3TvH j/ff4rV0TfL7OAOOAlfrpGjKkdMVqVylMMoSUspt6ZuIAgzA88KE1/MllYZrZBTxh/Dm5h r6PHT2NYqZGSN4JzlUa2CP8xqdNCNXE= X-Rspamd-Server: rspam11 X-Rspamd-Queue-Id: E283E400AE Authentication-Results: imf04.hostedemail.com; dkim=pass header.d=cmpxchg-org.20210112.gappssmtp.com header.s=20210112 header.b=pQcHZGMM; spf=pass (imf04.hostedemail.com: domain of hannes@cmpxchg.org designates 209.85.222.170 as permitted sender) smtp.mailfrom=hannes@cmpxchg.org; dmarc=pass (policy=none) header.from=cmpxchg.org X-Stat-Signature: 5a69fft7hac795nrbszn9c84m9qw6rbs X-Rspam-User: X-HE-Tag: 1659028990-345343 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Wed, Jul 27, 2022 at 09:16:08AM +0800, Huang, Ying wrote: > Aneesh Kumar K V writes: > > It is an abstract concept that indicates the performance of the > > device. As we learn more about which device attribute makes more impact in > > defining hierarchy, performance level will give more weightage to that specific > > attribute. It could be write latency or bandwidth. For me, distance has a direct > > linkage to latency because that is how we define numa distance now. Adding > > abstract to the name is not making it more abstract than perf_level. > > > > I am open to suggestions from others. Wei Xu has also suggested perf_level name. > > I can rename this to abstract_distance if that indicates the goal better. > > I'm open to naming. But I think that it's good to define it at some > degree instead of completely opaque stuff. If it's latency based, then > low value corresponds to high performance. If it's bandwidth based, > then low value corresponds to low performance. > > Hi, Wei and Johannes, > > What do you think about this? I'm also partial to distance. It's a familiar metric in non-uniform memory for guiding placement decisions, and that is how we continue to use it here too. It's historically meant bus latency, but given how the kernel perceives and acts on the metric IMO the term works just fine to express differences in bandwidth and chip resonpse times as well.