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 5759DC433EF for ; Thu, 21 Apr 2022 08:38:20 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F09BD6B0073; Thu, 21 Apr 2022 04:38:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E93256B0074; Thu, 21 Apr 2022 04:38:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D34676B0075; Thu, 21 Apr 2022 04:38:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.26]) by kanga.kvack.org (Postfix) with ESMTP id C38296B0073 for ; Thu, 21 Apr 2022 04:38:19 -0400 (EDT) Received: from smtpin27.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 99F4D269BF for ; Thu, 21 Apr 2022 08:38:19 +0000 (UTC) X-FDA: 79380234318.27.651765F Received: from outbound-smtp42.blacknight.com (outbound-smtp42.blacknight.com [46.22.139.226]) by imf25.hostedemail.com (Postfix) with ESMTP id C3962A0021 for ; Thu, 21 Apr 2022 08:38:15 +0000 (UTC) Received: from mail.blacknight.com (pemlinmail04.blacknight.ie [81.17.254.17]) by outbound-smtp42.blacknight.com (Postfix) with ESMTPS id 38F262368 for ; Thu, 21 Apr 2022 09:38:17 +0100 (IST) Received: (qmail 16182 invoked from network); 21 Apr 2022 08:38:17 -0000 Received: from unknown (HELO techsingularity.net) (mgorman@techsingularity.net@[84.203.198.246]) by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 21 Apr 2022 08:38:16 -0000 Date: Thu, 21 Apr 2022 09:38:11 +0100 From: Mel Gorman To: Matthew Wilcox Cc: Nicolas Saenz Julienne , Marcelo Tosatti , Vlastimil Babka , Michal Hocko , LKML , Linux-MM Subject: Re: [PATCH 1/6] mm/page_alloc: Add page->buddy_list and page->pcp_list Message-ID: <20220421083811.GA4105@techsingularity.net> References: <20220420095906.27349-1-mgorman@techsingularity.net> <20220420095906.27349-2-mgorman@techsingularity.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspam-User: X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: C3962A0021 X-Stat-Signature: b1xiue9y6x5rda7rd58zwcfsa3wfstg7 Authentication-Results: imf25.hostedemail.com; dkim=none; dmarc=none; spf=pass (imf25.hostedemail.com: domain of mgorman@techsingularity.net designates 46.22.139.226 as permitted sender) smtp.mailfrom=mgorman@techsingularity.net X-HE-Tag: 1650530295-880402 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, Apr 20, 2022 at 09:43:05PM +0100, Matthew Wilcox wrote: > On Wed, Apr 20, 2022 at 10:59:01AM +0100, Mel Gorman wrote: > > The page allocator uses page->lru for storing pages on either buddy or > > PCP lists. Create page->buddy_list and page->pcp_list as a union with > > page->lru. This is simply to clarify what type of list a page is on > > in the page allocator. > > Hi Mel, > > No objection to this change, and I certainly don't want to hold up > fixing this (or any other) problem in the page allocator. Minimally, I think the patch makes it easier to implement your suggestion and it can happen before or after the rest of the series. > I would > like to talk about splitting out free page management from struct page. > Maybe you'd like to discuss that in person at LSFMM, but a quick > sketch of a data structure might look like ... > Unfortunately, I am unable to attend LSF/MM (or any other conference) physically but I have no objection to splitting this out as a separate structure. I assume the basis for the change would be for type checking. > struct free_mem { > unsigned long __page_flags; page->flags, ok > union { > struct list_head buddy_list; > struct list_head pcp_list; > }; page->lru, ok > unsigned long __rsvd4; page->mapping, we need that > unsigned long pcp_migratetype_and_order; page->index, ok but more on this later > unsigned long buddy_order; page->private, ok. > unsigned int __page_type; page->_mapcount, we need that too. > atomic_t _refcount; page->_refcount, ok. > }; > > Am I missing anything there? > s/__page_flags/flags/ The allocator checks and modifies these bits so it has awareness of page->flags s/__rsvd4/mapping/ The mapping is checked for debugging and the allocator is responsible for clearing page->mapping s/pcp_migratetype_and_order/pcp_migratetype/ Commit 8b10b465d0e1 ("mm/page_alloc: free pages in a single pass during bulk free") removed the migratetype and order stuffing in page->index. The order is inferred from the array index via order_to_pindex and pindex_to_order but migratetype is still stored in page->index by set_pcppage_migratetype s/__page_type/_mapcount/ because _mapcount if checked for debugging memcg_data needs to be accessible for debugging checks _last_cpupid needs to be accessible as it's reset during prepare via page_cpupid_reset_last. Rather than putting in a dummy field for virtual, maybe virtual can move. > (Would you like to use separate types for pcp and buddy? That might be > overkill, or it might help keep the different stages of "free" memory > separate from each other) I think it's overkill because there is too much overlap between a PCP page and buddy page due to page checks and preparation. The distinguishing factor between a free pcp page and free buddy page is the PageBuddy bit. -- Mel Gorman SUSE Labs