Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp3838831imm; Mon, 30 Jul 2018 04:32:11 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcWqKG9DUDqgW0AajY1CF95YLOIy/ufp/XwJq37Y+CbX7jkcFBv9mlsYO0f80IWNoDUmAUd X-Received: by 2002:a17:902:7894:: with SMTP id q20-v6mr16413143pll.3.1532950331705; Mon, 30 Jul 2018 04:32:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532950331; cv=none; d=google.com; s=arc-20160816; b=0Y5nKdYFGQurSYU/5rPFoKTGoo4AJyzRVNB2ouUqmmLdnQsvInp7Ouvjt2n6GN/E5n LfDPt2wbFYy24Ar7j9Jr9bksM73ihCaetq4WvdymeR5QkyE1yC4xHeYb/E0jgFsiJQrT VPm2OHbqSqF1PolQCbndqtlLLruYjNgiAwy61OiOxDWiF3AFM0UBDt/yxH/e1PXUWjmZ kwS1BrPvYzmpy0AcZpPzE5PrWSok4yHW56s+rVRyyzSHKNNxx6xWHTqJfiYKF7imW58N UPD+1DF9jF1xi/OPhKALlf12H7No3ST8OM7jlDvqKiFRqFQBlUODpFQfLcpDjgyjLhvp AzrA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=I1tJKr1UmrJ89celS2bRGRYglKE7TYWUtbpY1gCCOJc=; b=Js6tbJncZeZ9fzY5zBrGdy+rIMlCkOwqVnd5fnBBrsO2gTgXWZYJfQP3kRaswOUh8H iHAPruib9RDpMfpjkrfeb80LIBSBIHQm2tU5Zmy7c5ehgMkSUK8p845dXfuX2onkma+R 72faPMEZD0hUnaBF91Z9kxMWGwxMYxuICV86ay17T/bNraD6lB8iDtxna4lh+Qqotoe8 ERMcYvtg2emBTFFqAfY5dNNuPjzBFXQWlijJGHYClFD6yNejgC8dMgkt4XaYhsubSuZG /BhRM2TZBcoPF1JVqncl+kVPCFyhERwnnbGMoKvpfHNvHRDnIpldvvNv/YFKcIbu9sqt ulYw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v7-v6si9516189plo.186.2018.07.30.04.31.57; Mon, 30 Jul 2018 04:32:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728777AbeG3NFG (ORCPT + 99 others); Mon, 30 Jul 2018 09:05:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:36296 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727018AbeG3NFG (ORCPT ); Mon, 30 Jul 2018 09:05:06 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id D2CECADFA; Mon, 30 Jul 2018 11:30:31 +0000 (UTC) Date: Mon, 30 Jul 2018 13:30:29 +0200 From: Michal Hocko To: David Hildenbrand Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Greg Kroah-Hartman , Ingo Molnar , Pavel Tatashin , Andrew Morton , Dan Williams , Jan Kara , Matthew Wilcox , =?iso-8859-1?B?Suly9G1l?= Glisse , Souptick Joarder , "Kirill A. Shutemov" , Vlastimil Babka , Oscar Salvador , YASUAKI ISHIMATSU , Mathieu Malaterre , Mel Gorman , Joonsoo Kim Subject: Re: [PATCH v1] mm: inititalize struct pages when adding a section Message-ID: <20180730113029.GM24267@dhcp22.suse.cz> References: <20180727165454.27292-1-david@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180727165454.27292-1-david@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 27-07-18 18:54:54, David Hildenbrand wrote: > Right now, struct pages are inititalized when memory is onlined, not > when it is added (since commit d0dc12e86b31 ("mm/memory_hotplug: optimize > memory hotplug")). > > remove_memory() will call arch_remove_memory(). Here, we usually access > the struct page to get the zone of the pages. > > So effectively, we access stale struct pages in case we remove memory that > was never onlined. So let's simply inititalize them earlier, when the > memory is added. We only have to take care of updating the zone once we > know it. We can use a dummy zone for that purpose. I have considered something like this when I was reworking memory hotplug to not associate struct pages with zone before onlining and I considered this to be rather fragile. I would really not like to get back to that again if possible. > So effectively, all pages will already be initialized and set to > reserved after memory was added but before it was onlined (and even the > memblock is added). We only inititalize pages once, to not degrade > performance. To be honest, I would rather see d0dc12e86b31 reverted. It is late in the release cycle and if the patch is buggy then it should be reverted rather than worked around. I found the optimization not really convincing back then and this is still the case TBH. -- Michal Hocko SUSE Labs