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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 ACB30C433E0 for ; Fri, 19 Feb 2021 11:25:00 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 1C40664E67 for ; Fri, 19 Feb 2021 11:25:00 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1C40664E67 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=suse.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 639138D001E; Fri, 19 Feb 2021 06:24:59 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 5EA018D000A; Fri, 19 Feb 2021 06:24:59 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 500878D001E; Fri, 19 Feb 2021 06:24:59 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0192.hostedemail.com [216.40.44.192]) by kanga.kvack.org (Postfix) with ESMTP id 34C7D8D000A for ; Fri, 19 Feb 2021 06:24:59 -0500 (EST) Received: from smtpin13.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 69181363F for ; Fri, 19 Feb 2021 11:24:57 +0000 (UTC) X-FDA: 77834785434.13.6A4BF51 Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf04.hostedemail.com (Postfix) with ESMTP id C55DF139 for ; Fri, 19 Feb 2021 11:24:55 +0000 (UTC) X-Virus-Scanned: by amavisd-new at test-mx.suse.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1613733895; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=lOOtfoPKE3BcGeguv92jXUEX7ahJX8CXJnXAjcq1auM=; b=vUpLLFtX5pt3E4q+IV/bVp4EkvDSaSxxtdGK8F/wywLbQpB4b8oEuL9pF4S5+pA7Jx2EWQ KGznwrWK9yktMtcxy/YWUsbUsaJkknjj5y5k2m1hP2SCReKR5ykl8/mdFs+2Ljo+DY8WSf A6s2KB45GB/wVlZsZn7QW9M9/FHHhbI= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BA0A1ACBF; Fri, 19 Feb 2021 11:24:55 +0000 (UTC) Date: Fri, 19 Feb 2021 12:24:54 +0100 From: Michal Hocko To: Oscar Salvador Cc: Andrew Morton , Mike Kravetz , David Hildenbrand , Muchun Song , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/2] mm: Make alloc_contig_range handle free hugetlb pages Message-ID: References: <20210218100917.GA4842@localhost.localdomain> <20210218133250.GA7983@localhost.localdomain> <20210219090548.GA17266@linux> <20210219103943.GA19945@linux> <20210219111703.GA20286@linux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210219111703.GA20286@linux> X-Stat-Signature: zbncbjch4i6bq3ucwz9ywzx3938tr43s X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: C55DF139 Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf04; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1613733895-164448 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 Fri 19-02-21 12:17:11, Oscar Salvador wrote: > On Fri, Feb 19, 2021 at 11:55:00AM +0100, Michal Hocko wrote: > > It is not the lock that I care about but more about counters. The > > intention was that there is a single place to handle both enqueing and > > dequeing. As not all places require counters to be updated. E.g. the > > migration which just replaces one page by another. > > I see. > alloc_fresh_huge_page->prep_new_huge_page increments h->nr_huge_pages{_node} > counters. > Which means: > > > new_page = alloc_fresh_huge_page(); > > if (!new_page) > > goto fail; > > spin_lock(hugetlb_lock); > > if (!PageHuge(old_page)) { > > /* freed from under us, nothing to do */ > > __update_and_free_page(new_page); > > Here we need update_and_free_page, otherwise we would be leaving a stale value > in h->nr_huge_pages{_node}. > > > goto unlock; > > } > > list_del(&old_page->lru); > > __update_and_free_page(old_page); > > Same here. > > > __enqueue_huge_page(new_page); > > This is ok since h->free_huge_pages{_node} do not need to be updated. Fair enough. I didn't get to think this through obviously, but you should get the idea ;) -- Michal Hocko SUSE Labs