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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 275DCC34056 for ; Wed, 19 Feb 2020 20:08:14 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id D997A24654 for ; Wed, 19 Feb 2020 20:08:13 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="U4t0+1H9" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D997A24654 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 846246B0003; Wed, 19 Feb 2020 15:08:13 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 7D0136B0006; Wed, 19 Feb 2020 15:08:13 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 6BEFA6B0007; Wed, 19 Feb 2020 15:08:13 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0138.hostedemail.com [216.40.44.138]) by kanga.kvack.org (Postfix) with ESMTP id 513CA6B0003 for ; Wed, 19 Feb 2020 15:08:13 -0500 (EST) Received: from smtpin15.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id 09F45181AC9CB for ; Wed, 19 Feb 2020 20:08:13 +0000 (UTC) X-FDA: 76507963266.15.kick67_81e469f5cc605 X-HE-Tag: kick67_81e469f5cc605 X-Filterd-Recvd-Size: 2382 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf08.hostedemail.com (Postfix) with ESMTP for ; Wed, 19 Feb 2020 20:08:12 +0000 (UTC) Received: from X1 (nat-ab2241.sltdut.senawave.net [162.218.216.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 842F32176D; Wed, 19 Feb 2020 20:08:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582142891; bh=K/D5JbPk2+EBYp2gmQA0q9ditYqXaZ6u/jNNJaQQNeU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=U4t0+1H9+T91595fwF5FJlrfN5hAP7b2OvyDrCSy3zwLJrvS07mTsYuEM5DXHnFGp 4qFSz1jxRax7qvwJ19FfAf+jYHr05omtkY3xWKa9Bat7iEgGBVKKyg8tHE6D0KUotm JV5ctKrnTkl+82JgBHttCq5MEna+P72IO2uvUTbE= Date: Wed, 19 Feb 2020 12:08:10 -0800 From: Andrew Morton To: Wei Yang Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, rientjes@google.com, mhocko@kernel.org Subject: Re: [Patch v4] mm/vmscan.c: remove cpu online notification for now Message-Id: <20200219120810.c7677fa58594f5423549f59d@linux-foundation.org> In-Reply-To: <20200218224422.3407-1-richardw.yang@linux.intel.com> References: <20200218224422.3407-1-richardw.yang@linux.intel.com> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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, 19 Feb 2020 06:44:22 +0800 Wei Yang wrote: > kswapd kernel thread starts either with a CPU affinity set to the full > cpu mask of its target node or without any affinity at all if the node > is CPUless. There is a cpu hotplug callback (kswapd_cpu_online) that > implements an elaborate way to update this mask when a cpu is onlined. > > It is not really clear whether there is any actual benefit from this > scheme. Completely CPU-less NUMA nodes rarely gain a new CPU during > runtime. This is the case across all platforms, all architectures, all users for the next N years? I'm surprised that we know this with sufficient confidence. Can you explain how you came to make this assertion? > Drop the code for that reason. If there is a real usecase then > we can resurrect and simplify the code.