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 345E7C433F5 for ; Thu, 24 Feb 2022 00:06:09 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A36338D0002; Wed, 23 Feb 2022 19:06:08 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 9BDAE8D0001; Wed, 23 Feb 2022 19:06:08 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 869038D0002; Wed, 23 Feb 2022 19:06:08 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0250.hostedemail.com [216.40.44.250]) by kanga.kvack.org (Postfix) with ESMTP id 581D68D0001 for ; Wed, 23 Feb 2022 19:06:08 -0500 (EST) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id DB209181CEEB6 for ; Thu, 24 Feb 2022 00:06:07 +0000 (UTC) X-FDA: 79175730774.23.FBCF5F4 Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by imf02.hostedemail.com (Postfix) with ESMTP id CF9E38000E for ; Thu, 24 Feb 2022 00:06:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645661167; x=1677197167; h=message-id:date:mime-version:to:cc:references:from: subject:in-reply-to:content-transfer-encoding; bh=Uu+jTVal72wWHq+zRSDpCjRHJopUoZhOIPfQFDisbtU=; b=YDZ/WfEwrJFYVEEnDtClBU7RLiMP0BK8r4dQIQw9cYIrbFVVQPPipV1L +EXjSXlXkyNtH4vmsSvHqquwFgOoOJgmqFrTGz1vbRLO9cFQPQNPnFFal 30D+SOoJ3Z4VQ+3zhyUl7eOa6DdHDoFKMXCD07WJH/Xb+0wD3kwOz7p7F /Imb2iqJzgy7ggDfCbvdXPNhpJvh26R5Xy923J68KdVtqXIZMQTEYtCWU uTP0mWub8mtMKdL34+mc5p8V9aF2Ab4gfCE7azx0UV89u7XpktOxly1Oi btUwqBhPHukz0L85smqrvy/RNOppDzBJspG4wMTV2GnI2acTjCxwtMjfr w==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="251847834" X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="251847834" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 16:06:04 -0800 X-IronPort-AV: E=Sophos;i="5.88,392,1635231600"; d="scan'208";a="491398664" Received: from chakanog-mobl.amr.corp.intel.com (HELO [10.212.198.215]) ([10.212.198.215]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 16:06:03 -0800 Message-ID: Date: Wed, 23 Feb 2022 16:05:59 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: Abhishek Goel , Dave Hansen Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Zi Yan , David Hildenbrand , Yang Shi , Huang Ying , Andrew Morton References: <20210721063926.3024591-1-ying.huang@intel.com> <20210721063926.3024591-2-ying.huang@intel.com> From: Dave Hansen Subject: Re: [PATCH -V11 2/9] mm/migrate: update node demotion order on hotplug events In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspam-User: Authentication-Results: imf02.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b="YDZ/WfEw"; spf=none (imf02.hostedemail.com: domain of dave.hansen@intel.com has no SPF policy when checking 134.134.136.24) smtp.mailfrom=dave.hansen@intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: CF9E38000E X-Stat-Signature: bmgba9hjae9bbba5f5uwmjhihj3676uz X-HE-Tag: 1645661165-766827 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 2/23/22 15:02, Abhishek Goel wrote: > If needed, I will provide experiment results and traces that were used > to conclude this. It would be great if you can provide some more info. Even just a CPU time profile would be helpful. It would also be great to understand more about what "hotplug on power systems" actually means. Is this a synthetic benchmark, or are actual end-users running into this issue? Are entire nodes of CPUs going offline? Or is this just doing an offline/online of CPU 22 in a 100-CPU NUMA node?