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 38435C433DB for ; Mon, 15 Feb 2021 10:33:08 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id C34BB64E6D for ; Mon, 15 Feb 2021 10:33:07 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C34BB64E6D 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 3428F8D00ED; Mon, 15 Feb 2021 05:33:07 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 31ABC8D00E6; Mon, 15 Feb 2021 05:33:07 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 2080B8D00ED; Mon, 15 Feb 2021 05:33:07 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0047.hostedemail.com [216.40.44.47]) by kanga.kvack.org (Postfix) with ESMTP id 0B51B8D00E6 for ; Mon, 15 Feb 2021 05:33:07 -0500 (EST) Received: from smtpin10.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id C15128248047 for ; Mon, 15 Feb 2021 10:33:06 +0000 (UTC) X-FDA: 77820139572.10.79F75AF Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by imf01.hostedemail.com (Postfix) with ESMTP id EC1D520001D6 for ; Mon, 15 Feb 2021 10:33:05 +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=1613385185; 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=5VOUPmXPZzeS6nM2Yw1Dqr1Wa/BJdfFT6ZPLkwHsXto=; b=BJcggBbOIeuRofSc2tjGIErH5zKllt9x1z9zms4Zs5MQ+OpM+rswGyh4BYXla/4ahQLnh4 OXg74SFAnOtr3aSdCPBAyuOKLw4kSUKDaPBPZYFbyXBwp0KgV7h6/rMbeS+BvSn2Z0Wdax VED9JvEeS6lPuZN2UhkQR5SQjfJCms0= Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id E3421AC32; Mon, 15 Feb 2021 10:33:04 +0000 (UTC) Date: Mon, 15 Feb 2021 11:33:03 +0100 From: Michal Hocko To: Muchun Song Cc: Jonathan Corbet , Mike Kravetz , Thomas Gleixner , mingo@redhat.com, bp@alien8.de, x86@kernel.org, hpa@zytor.com, dave.hansen@linux.intel.com, luto@kernel.org, Peter Zijlstra , viro@zeniv.linux.org.uk, Andrew Morton , paulmck@kernel.org, mchehab+huawei@kernel.org, pawan.kumar.gupta@linux.intel.com, Randy Dunlap , oneukum@suse.com, anshuman.khandual@arm.com, jroedel@suse.de, Mina Almasry , David Rientjes , Matthew Wilcox , Oscar Salvador , "Song Bao Hua (Barry Song)" , David Hildenbrand , HORIGUCHI =?utf-8?B?TkFPWUEo5aCA5Y+jIOebtOS5nyk=?= , Joao Martins , Xiongchun duan , linux-doc@vger.kernel.org, LKML , Linux Memory Management List , linux-fsdevel Subject: Re: [External] Re: [PATCH v15 4/8] mm: hugetlb: alloc the vmemmap pages associated with each HugeTLB page Message-ID: References: <20210208085013.89436-1-songmuchun@bytedance.com> <20210208085013.89436-5-songmuchun@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Stat-Signature: ppjggwhticy31idb1x8ck1br9gfnhuor X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: EC1D520001D6 Received-SPF: none (suse.com>: No applicable sender policy available) receiver=imf01; identity=mailfrom; envelope-from=""; helo=mx2.suse.de; client-ip=195.135.220.15 X-HE-DKIM-Result: pass/pass X-HE-Tag: 1613385185-360678 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 Mon 15-02-21 18:05:06, Muchun Song wrote: > On Fri, Feb 12, 2021 at 11:32 PM Michal Hocko wrote: [...] > > > +int alloc_huge_page_vmemmap(struct hstate *h, struct page *head) > > > +{ > > > + int ret; > > > + unsigned long vmemmap_addr = (unsigned long)head; > > > + unsigned long vmemmap_end, vmemmap_reuse; > > > + > > > + if (!free_vmemmap_pages_per_hpage(h)) > > > + return 0; > > > + > > > + vmemmap_addr += RESERVE_VMEMMAP_SIZE; > > > + vmemmap_end = vmemmap_addr + free_vmemmap_pages_size_per_hpage(h); > > > + vmemmap_reuse = vmemmap_addr - PAGE_SIZE; > > > + > > > + /* > > > + * The pages which the vmemmap virtual address range [@vmemmap_addr, > > > + * @vmemmap_end) are mapped to are freed to the buddy allocator, and > > > + * the range is mapped to the page which @vmemmap_reuse is mapped to. > > > + * When a HugeTLB page is freed to the buddy allocator, previously > > > + * discarded vmemmap pages must be allocated and remapping. > > > + */ > > > + ret = vmemmap_remap_alloc(vmemmap_addr, vmemmap_end, vmemmap_reuse, > > > + GFP_ATOMIC | __GFP_NOWARN | __GFP_THISNODE); > > > > I do not think that this is a good allocation mode. GFP_ATOMIC is a non > > sleeping allocation and a medium memory pressure might cause it to > > fail prematurely. I do not think this is really an atomic context which > > couldn't afford memory reclaim. I also do not think we want to grant > > Because alloc_huge_page_vmemmap is called under hugetlb_lock > now. So using GFP_ATOMIC indeed makes the code more simpler. You can have a preallocated list of pages prior taking the lock. Moreover do we want to manipulate vmemmaps from under spinlock in general. I have to say I have missed that detail when reviewing. Need to think more. > From the document of the kernel, I learned that __GFP_NOMEMALLOC > can be used to explicitly forbid access to emergency reserves. So if > we do not want to use the reserve memory. How about replacing it to > > GFP_ATOMIC | __GFP_NOMEMALLOC | __GFP_NOWARN | __GFP_THISNODE The whole point of GFP_ATOMIC is to grant access to memory reserves so the above is quite dubious. If you do not want access to memory reserves then use GFP_NOWAIT instead. But failures are much more easier to happen then. NOMEMALLOC is meant to be used from paths which are allowed to consume memory reserves - e.g. when invoked from the memory reclaim path. -- Michal Hocko SUSE Labs