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 4EB9CC433F5 for ; Mon, 18 Apr 2022 15:34:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5613A8D0011; Mon, 18 Apr 2022 11:34:41 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 511456B00B4; Mon, 18 Apr 2022 11:34:41 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 3D8DA8D0011; Mon, 18 Apr 2022 11:34:41 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.a.hostedemail.com [64.99.140.24]) by kanga.kvack.org (Postfix) with ESMTP id 2C1946B00B3 for ; Mon, 18 Apr 2022 11:34:41 -0400 (EDT) Received: from smtpin19.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay12.hostedemail.com (Postfix) with ESMTP id E4391121EF7 for ; Mon, 18 Apr 2022 15:34:40 +0000 (UTC) X-FDA: 79370397120.19.517E19F Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by imf22.hostedemail.com (Postfix) with ESMTP id D806EC0004 for ; Mon, 18 Apr 2022 15:34:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650296079; x=1681832079; h=message-id:date:mime-version:to:references:from:subject: in-reply-to:content-transfer-encoding; bh=SRNvMB6bOZswif/I19QJA25IGhzgKY/S8qZnWPXx9sg=; b=E7LqHdlqgQZwIWt+z6P17y+W5htWtDmmSAYTfJX1kGMGEVr9gAXHCMA5 vvm6XrizWucwsjRQMUIkliBBZJ4Zn7FZKXN7Orcq1tAKHv2U0OwYksQzn 6TULUHGxYncCs3TFtuv9iDj9j63ljIHHIaBIKUhXpx5+fjrg/0eY0jiKE ap386PGX7r/tEqGybB0j0XoQzRJXzB424jxhO4iHY26JhWzU4qYRXkVDm ifiLYNrgsjksAo5mGaTAt1ZZ72Ek9WM0/ac343+CEuMHXJkxKpd82wzOU bBAetymJruwRO1ZqbTZ3WClfSf4GpPZ44fD/HBentb4bkVPNWH05uLd+E A==; X-IronPort-AV: E=McAfee;i="6400,9594,10321"; a="263301855" X-IronPort-AV: E=Sophos;i="5.90,270,1643702400"; d="scan'208";a="263301855" Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Apr 2022 08:34:38 -0700 X-IronPort-AV: E=Sophos;i="5.90,270,1643702400"; d="scan'208";a="554276474" Received: from cebrown-mobl.amr.corp.intel.com (HELO [10.212.18.136]) ([10.212.18.136]) by orsmga007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Apr 2022 08:34:36 -0700 Message-ID: Date: Mon, 18 Apr 2022 08:34:36 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-US To: linux-mm@kvack.org, mhocko@kernel.org, akpm@linux-foundation.org, rientjes@google.com, yosryahmed@google.com, hannes@cmpxchg.org, shakeelb@google.com, dave.hansen@linux.intel.com, tim.c.chen@linux.intel.com, roman.gushchin@linux.dev, gthelen@google.com, a.manzanares@samsung.com, heekwon.p@samsung.com, gim.jongmin@samsung.com, linux-kernel@vger.kernel.org References: <20220416053902.68517-1-dave@stgolabs.net> <20220417034932.jborenmvfbqrfhlj@offworld> From: Dave Hansen Subject: Re: [PATCH 6/6] mm/migrate: export whether or not node is toptier in sysf In-Reply-To: <20220417034932.jborenmvfbqrfhlj@offworld> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=E7LqHdlq; dmarc=pass (policy=none) header.from=intel.com; spf=none (imf22.hostedemail.com: domain of dave.hansen@intel.com has no SPF policy when checking 134.134.136.65) smtp.mailfrom=dave.hansen@intel.com X-Rspam-User: X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: D806EC0004 X-Stat-Signature: pfkgpyah3f313bjgy56dazkad5z1z1mc X-HE-Tag: 1650296079-195993 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000025, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 4/16/22 20:49, Davidlohr Bueso wrote: > This allows userspace to know if the node is considered fast > memory (with CPUs attached to it). While this can be already > derived without a new file, this helps further encapsulate the > concept. What is userspace supposed to *do* with this, though? What does "attached" mean? Isn't it just asking for trouble to add (known) redundancy to the ABI? It seems like a recipe for future inconsistency.