Received: by 2002:a05:7412:3784:b0:e2:908c:2ebd with SMTP id jk4csp1546250rdb; Mon, 2 Oct 2023 13:02:09 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHmzdH/9pCg2bZSMHQvL4YGtqNswRAmsqsmQnMncsr/D2VRaJpout/5rBMsmE1FuH7hrO1U X-Received: by 2002:a05:6a00:22cc:b0:690:cb8f:3320 with SMTP id f12-20020a056a0022cc00b00690cb8f3320mr14042535pfj.24.1696276928825; Mon, 02 Oct 2023 13:02:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1696276928; cv=none; d=google.com; s=arc-20160816; b=lMNvMPwMcpJuN44V3oYw+MBMK/ArZsRjYAk3+QSEQsxfGTjrWk9Mz6O9dK8/z68gZU IJuzAAMV7IybKBWLj3rUcxHuZWOy+096qFEyEXH33muujqXOdCCxzM5vm7J3BftMQ/Ja /E0+UVrbEAweDdgkbdCO8+21ADByb2WlzM63NZWtbCFB8VgXTVghyddX21yfQT2Vt0RL YG6k40zmLRphJqgAYzSYzMUoYJPS33EhT+BiZlVS9Yyf/OKizpJSwL7T9IO8BkhrgEbe zYG3i8SCUpNyCPHqTp10uB2X4/VfTxxBdawD9BD28Iifv1AGbb+pkalA7pKkO63Mp74o f6LA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :organization:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:dkim-signature; bh=bOneOzTrSmpqtG0qhnCChNvIYEoW+1fDAEnSmXjPvzQ=; fh=n7G6AZo1L2xNczpld7wlZiXV8C2lWRuKcUzrGMy9D4A=; b=POIFiSEpEdhK9lCsnHW5KVXBl8bxlZJqQUq0fwxXIm3TH0Y5iwWhtvp18J+M/22wfJ f5+NCH8vb5msG7GhHQOnyK95FYW71wVz9qDI3y1Y8IlHdjJWpA6xnoPVNKJi9Qz68wMX 25anmXPkGXUSqh1U9s+biU0wSADcW4nOtYKN4pxqMShkbrQqBrHKmMmIdPNODzPrix5B uEb8qcroguR1iI/b27FkeuH2XH1tLvxIDizwn3MV7RMsIyMWLCkrWlu/4f2s9qYlA+8s 4fGjObQE4/StkK30Y3PYuLnvi0E/HjsABeWwp1njxv1MYhul9pO1J2jTW4/tJ5yf9Lj1 ChYw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Cvn9G8fn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id p30-20020a63741e000000b00582dcfe3b41si19416672pgc.374.2023.10.02.13.02.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Oct 2023 13:02:08 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Cvn9G8fn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id DA8F4808496F; Mon, 2 Oct 2023 04:26:19 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.10 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236638AbjJBL0L (ORCPT + 99 others); Mon, 2 Oct 2023 07:26:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37806 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231290AbjJBL0K (ORCPT ); Mon, 2 Oct 2023 07:26:10 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 270D8BF for ; Mon, 2 Oct 2023 04:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1696245917; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=bOneOzTrSmpqtG0qhnCChNvIYEoW+1fDAEnSmXjPvzQ=; b=Cvn9G8fnYsPDf4Mko80mJmMx5g/W0lPSovuCnr0RjPd9vkMSytu7c2bxKRA9BqITNg42GG k31yXPHCFLtYTqn5kOpuDEPVCGUL6t0kad7BiRBdmTKLoyA2d2YcWIsiIBtkQb4crK/s/C 9yn+WebLekHUZchKkzMarLbfgmmMY68= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-435-c0umF5xDNF2op-KTGMnfUQ-1; Mon, 02 Oct 2023 07:25:13 -0400 X-MC-Unique: c0umF5xDNF2op-KTGMnfUQ-1 Received: by mail-wm1-f70.google.com with SMTP id 5b1f17b1804b1-4054743df06so126867725e9.3 for ; Mon, 02 Oct 2023 04:25:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696245912; x=1696850712; h=content-transfer-encoding:in-reply-to:organization:from:references :cc:to:content-language:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=bOneOzTrSmpqtG0qhnCChNvIYEoW+1fDAEnSmXjPvzQ=; b=Yrm4BhIvC3YVUzG/a2FACqmwyhDfvfo1pvKFIMhyHzrBy/moc86c5x1SJxSzvwPSEE sWpViJyLWaUTkiOcvK/EGyE0JrkvE5SieAyQzHJbt6acMhuohmKVUssL6ppJgcznnkj5 XAcj2a5TvcajmNLS53TNJbeqIgX1VnBzJYZbPcDtd5rm0SKABX/ADGyS7Q983JXmrvKo Z3Ip5ZlgUEWrvKkmGHj0iwz53LrLOlRfwkidWStH5MXDTL+M+/0EkCHvtQWEp/fb+i24 K8N2C0aWkpRff3SOVjC80+OtfdUmCo1q35kLOIfudM4oWzJs1pNiVkb5dsyWotI9BatV IKxw== X-Gm-Message-State: AOJu0Ywqcun5Z+RDqCmM0+duuWSFkNlrPqD81BNJvl2BdJxQsst1fW5M BWo/P1sHYlg+WuPzGShaS9BG7RhUY4cC2ol6dDENH33ePFlUVYH+WowyNL08HXbLGa7FKG0XueP pyGul3NwuJl43tdovvZ5QRGm5 X-Received: by 2002:a1c:7204:0:b0:405:2e28:4878 with SMTP id n4-20020a1c7204000000b004052e284878mr9305396wmc.30.1696245912662; Mon, 02 Oct 2023 04:25:12 -0700 (PDT) X-Received: by 2002:a1c:7204:0:b0:405:2e28:4878 with SMTP id n4-20020a1c7204000000b004052e284878mr9305375wmc.30.1696245912165; Mon, 02 Oct 2023 04:25:12 -0700 (PDT) Received: from ?IPV6:2003:cb:c735:f200:cb49:cb8f:88fc:9446? (p200300cbc735f200cb49cb8f88fc9446.dip0.t-ipconnect.de. [2003:cb:c735:f200:cb49:cb8f:88fc:9446]) by smtp.gmail.com with ESMTPSA id t9-20020a7bc3c9000000b003feae747ff2sm7016568wmj.35.2023.10.02.04.25.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Oct 2023 04:25:11 -0700 (PDT) Message-ID: <3057dab3-19f2-99ca-f125-e91a094975ed@redhat.com> Date: Mon, 2 Oct 2023 13:25:02 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: [PATCH v4 2/2] mm: Init page count in reserve_bootmem_region when MEMINIT_EARLY Content-Language: en-US To: Mike Rapoport Cc: Yajun Deng , akpm@linux-foundation.org, mike.kravetz@oracle.com, muchun.song@linux.dev, willy@infradead.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20230928083302.386202-1-yajun.deng@linux.dev> <20230928083302.386202-3-yajun.deng@linux.dev> <20230929083018.GU3303@kernel.org> <20230929100252.GW3303@kernel.org> <15233624-f32e-172e-b2f6-7ca7bffbc96d@linux.dev> <20231001185934.GX3303@kernel.org> <90342474-432a-9fe3-2f11-915a04f0053f@linux.dev> <20231002084708.GZ3303@kernel.org> <20231002111051.GA3303@kernel.org> From: David Hildenbrand Organization: Red Hat In-Reply-To: <20231002111051.GA3303@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Mon, 02 Oct 2023 04:26:20 -0700 (PDT) On 02.10.23 13:10, Mike Rapoport wrote: > On Mon, Oct 02, 2023 at 10:56:51AM +0200, David Hildenbrand wrote: >> On 02.10.23 10:47, Mike Rapoport wrote: >>> On Mon, Oct 02, 2023 at 03:03:56PM +0800, Yajun Deng wrote: >>>> >>>> On 2023/10/2 02:59, Mike Rapoport wrote: >>>>> On Fri, Sep 29, 2023 at 06:27:25PM +0800, Yajun Deng wrote: >>>>>> On 2023/9/29 18:02, Mike Rapoport wrote: >>>>>>>>>> diff --git a/mm/page_alloc.c b/mm/page_alloc.c >>>>>>>>>> index 06be8821d833..b868caabe8dc 100644 >>>>>>>>>> --- a/mm/page_alloc.c >>>>>>>>>> +++ b/mm/page_alloc.c >>>>>>>>>> @@ -1285,18 +1285,22 @@ void __free_pages_core(struct page *page, unsigned int order) >>>>>>>>>> unsigned int loop; >>>>>>>>>> /* >>>>>>>>>> - * When initializing the memmap, __init_single_page() sets the refcount >>>>>>>>>> - * of all pages to 1 ("allocated"/"not free"). We have to set the >>>>>>>>>> - * refcount of all involved pages to 0. >>>>>>>>>> + * When initializing the memmap, memmap_init_range sets the refcount >>>>>>>>>> + * of all pages to 1 ("reserved" and "free") in hotplug context. We >>>>>>>>>> + * have to set the refcount of all involved pages to 0. Otherwise, >>>>>>>>>> + * we don't do it, as reserve_bootmem_region only set the refcount on >>>>>>>>>> + * reserve region ("reserved") in early context. >>>>>>>>>> */ >>>>>>>>> Again, why hotplug and early init should be different? >>>>>>>> I will add a comment that describes it will save boot time. >>>>>>> But why do we need initialize struct pages differently at boot time vs >>>>>>> memory hotplug? >>>>>>> Is there a reason memory hotplug cannot have page count set to 0 just like >>>>>>> for pages reserved at boot time? >>>>>> This patch just save boot time in MEMINIT_EARLY. If someone finds out that >>>>>> it can save time in >>>>>> >>>>>> MEMINIT_HOTPLUG, I think it can be done in another patch later. I just >>>>>> keeping it in the same. >>>>> But it's not the same. It becomes slower after your patch and the code that >>>>> frees the pages for MEMINIT_EARLY and MEMINIT_HOTPLUG becomes non-uniform >>>>> for no apparent reason. >>>> >>>> __free_pages_core will also be called by others, such as: >>>> deferred_free_range, do_collection and memblock_free_late. >>>> >>>> We couldn't removeĀ  'if (page_count(page))' even if we set page count to 0 >>>> when MEMINIT_HOTPLUG. >>> >>> That 'if' breaks the invariant that __free_pages_core is always called for >>> pages with initialized page count. Adding it may lead to subtle bugs and >>> random memory corruption so we don't want to add it at the first place. >> >> As long as we have to special-case memory hotplug, we know that we are >> always coming via generic_online_page() in that case. We could either move >> some logic over there, or let __free_pages_core() know what it should do. > > Looks like the patch rather special cases MEMINIT_EARLY, although I didn't > check throughfully other code paths. > Anyway, relying on page_count() to be correct in different ways for > different callers of __free_pages_core() does not sound right to me. Absolutely agreed. -- Cheers, David / dhildenb