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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9BDF9C05027 for ; Tue, 14 Feb 2023 12:46:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232468AbjBNMqo (ORCPT ); Tue, 14 Feb 2023 07:46:44 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33378 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232457AbjBNMqi (ORCPT ); Tue, 14 Feb 2023 07:46:38 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B7A1265AD for ; Tue, 14 Feb 2023 04:46:33 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id EAA646160D for ; Tue, 14 Feb 2023 12:46:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C5A2DC433EF; Tue, 14 Feb 2023 12:46:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1676378792; bh=rvY4akbiWkPYp6q8TWHxBXJMkGaOh5UByiYweshK5tA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=FjxqQOiRowx5Ag6MmnJWY6fYnMyjiQGyRcgh+5Pr68OuA7WEiVwZRZqvHobwGGilk DlwtE+gG9pN2nP2YsEX8CJ0A5YMyBJg5W7KG6ZXMc6aV1aN8swwKBHMB6L89uHZMYI E1WJmP03hDrL3JMXB/VI3kFB8Zl3IfxxfDZsgbay0LyW3YllOtgcbfQIxioWS75m8U x7KmzQ8vPmgoJ1HZKTcU0KxDQzBVw3CjFDRrDJgfnU8rF3I4HvAAGP6CpiGllUBmOH rW4O/sxWZXV26FCteWRJh/DLEq+X/27QKFLgbCIS4TCrQfExuCH/mL2X3+rJ5wcV7h 3ArohJk4pKGMw== Date: Tue, 14 Feb 2023 14:46:17 +0200 From: Mike Rapoport To: David Hildenbrand Cc: Qi Zheng , Qi Zheng , Vlastimil Babka , akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Teng Hu , Matthew Wilcox , Mel Gorman , Oscar Salvador , Muchun Song , x86@kernel.org Subject: Re: [PATCH] mm: page_alloc: don't allocate page from memoryless nodes Message-ID: References: <2484666e-e78e-549d-e075-b2c39d460d71@suse.cz> <85af4ada-96c8-1f99-90fa-9b6d63d0016e@bytedance.com> <67240e55-af49-f20a-2b4b-b7d574cd910d@gmail.com> <22f0e262-982e-ea80-e52a-a3c924b31d58@redhat.com> <4386151c-0328-d207-9a71-933ef61817f9@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Now added x86 folks for real :) The thread starts here: https://lore.kernel.org/all/20230212110305.93670-1-zhengqi.arch@bytedance.com/ On Tue, Feb 14, 2023 at 01:44:06PM +0200, Mike Rapoport wrote: > (added x86 folks) > > On Tue, Feb 14, 2023 at 12:29:42PM +0100, David Hildenbrand wrote: > > On 14.02.23 12:26, Qi Zheng wrote: > > > On 2023/2/14 19:22, David Hildenbrand wrote: > > > > > > > > TBH, this is the first time I hear of NODE_MIN_SIZE and it seems to be a > > > > pretty x86 specific thing. > > > > > > > > Are we sure we want to get NODE_MIN_SIZE involved? > > > > > > Maybe add an arch_xxx() to handle it? > > > > I still haven't figured out what we want to achieve with NODE_MIN_SIZE at > > all. It smells like an arch-specific hack looking at > > > > "Don't confuse VM with a node that doesn't have the minimum amount of > > memory" > > > > Why shouldn't mm-core deal with that? > > Well, a node with <4M RAM is not very useful and bears all the overhead of > an extra live node. > > But, hey, why won't we just drop that '< NODE_MIN_SIZE' and let people with > weird HW configurations just live with this? > > > I'd appreciate an explanation of the bigger picture, what the issue is and > > what the approach to solve it is (including memory onlining/offlining). > > > > -- > > Thanks, > > > > David / dhildenb > > > > -- > Sincerely yours, > Mike. > -- Sincerely yours, Mike.