Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp1894228imm; Thu, 27 Sep 2018 04:21:26 -0700 (PDT) X-Google-Smtp-Source: ACcGV60KD704RdHA9iHokJN9ND+MojvhKjGVkWWSHsfbioQA+PJ0NW1Icsywj0uB5c1WEa0xEtUx X-Received: by 2002:a65:588e:: with SMTP id d14-v6mr4252383pgu.117.1538047286689; Thu, 27 Sep 2018 04:21:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538047286; cv=none; d=google.com; s=arc-20160816; b=hfqzYDEyofQ1oc2JAX/WhS/ZahCNdHwmtr77D+qs6oiym/J6v6AeFrc+NRCq4pKrrh nuYQ9l/HdOXk18KicDLdhsnI54PX6TyOWv1YHaclSeL8i6+h1/ebdQp3pz9aloW/oAtj BM+27lNpi4iE0BpuUF7DyazCHS8p4/Y/Z5QGlBZSNTzUkPSlXBLUOlZ7pKqrUmXFj/0E U7YK1v61292K7bomSoaSHHBtnC9E1p3tH73PRlFOb/4gastPY/aiim7G9rQzTje+tayE +NvG6uwaWpa2T8hivyOcV4u4eVEIFqy0fGjd35d/GzXIcz6VsOxVNMd0lDz6Y/1QKBoP 6BJA== 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; bh=LHWr/QbvANj79qBF35O6xH1LDv5YPVsp73hK4pe3i5k=; b=R8YJp00zzjL+pKuw8qTXPuH39Xcc22O7PNs0KfsfrWraUiiCbrMIqXkrhwOgk9yZpY lgZckP6XIdX1V2jJj1i3Hqu99rJdnmqoaEXOqg3G0lUvpqcsfnhM03gka6j59LhKnYtG LVhvKNiPR2sRvtIJOEuwUABjt41rSZ9/UVw5r/COaJMaJmbyMpiIJMIcAu34Q4mYRYVY XBs5I63qZiNKsq4G8W3jEVbWfWhbK4UGhLkb4wG/00TPWmU+60WQyg4cCqaG+TCivdIP TKYHVIamilT72itO/GawcFN/O6IlaNCwOe/7T+w8AfhZjKY3m4w4scouCT5phnA9hgac oBxQ== 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 68-v6si1819293pla.496.2018.09.27.04.21.11; Thu, 27 Sep 2018 04:21:26 -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 S1727504AbeI0Ria (ORCPT + 99 others); Thu, 27 Sep 2018 13:38:30 -0400 Received: from mx2.suse.de ([195.135.220.15]:33724 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727272AbeI0Ria (ORCPT ); Thu, 27 Sep 2018 13:38:30 -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 B75AFB0F4; Thu, 27 Sep 2018 11:20:41 +0000 (UTC) Date: Thu, 27 Sep 2018 13:20:41 +0200 From: Michal Hocko To: Dan Williams Cc: alexander.h.duyck@linux.intel.com, Linux MM , Andrew Morton , Linux Kernel Mailing List , linux-nvdimm , Pasha Tatashin , Dave Jiang , Dave Hansen , =?iso-8859-1?B?Suly9G1l?= Glisse , rppt@linux.vnet.ibm.com, Logan Gunthorpe , Ingo Molnar , "Kirill A. Shutemov" Subject: Re: [PATCH v5 4/4] mm: Defer ZONE_DEVICE page initialization to the point where we init pgmap Message-ID: <20180927112041.GG6278@dhcp22.suse.cz> References: <20180925200551.3576.18755.stgit@localhost.localdomain> <20180925202053.3576.66039.stgit@localhost.localdomain> <20180926075540.GD6278@dhcp22.suse.cz> <6f87a5d7-05e2-00f4-8568-bb3521869cea@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Wed 26-09-18 11:52:56, Dan Williams wrote: [...] > Could we push the hotplug lock deeper to the places that actually need > it? What I found with my initial investigation is that we don't even > need the hotplug lock for the vmemmap initialization with this patch > [1]. Yes, the scope of the hotplug lock should be evaluated and _documented_. Then we can build on top. -- Michal Hocko SUSE Labs