Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp446673imm; Wed, 18 Jul 2018 05:07:01 -0700 (PDT) X-Google-Smtp-Source: AAOMgpfNyt3OtUiPr8tquETdcRWi1DleCl5qJ8BPzOI5UNJG9RNK2KJNsdKalV7m9J0Gm+wvsIqO X-Received: by 2002:a17:902:42a3:: with SMTP id h32-v6mr5638339pld.72.1531915620993; Wed, 18 Jul 2018 05:07:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531915620; cv=none; d=google.com; s=arc-20160816; b=UQd/k/rRQxYI/Q3fK4RjpJ0V/9g5RyD+xB+c/sRjsVXHF5uz4jFTBFjgeJmXAeU5FJ bpGYh563gw6CmyzR3fXimmNSQR6n63QheyjIIE2xBdn5ZZ22vhJwLM/uwQZ8gt2Ylexi 2Ffi03ohMuCvNUQHKVHUl1IbHTyEe2fdkKD5YYDIJ6c2PfAfG/qJOSFa519ilVQTNodr xFWEJtJQTbv+VcoizSX84uNyQtDsikJcmnYpFSFLR8qzmvCkxGbgKDt12SZRyHxQrYCt I4jYtVpqYVRz962YTiSm6cAi5YaGFtaJPjzf4sVwphfYnkRhI/o/6hXc/ycWXzpg14xG DjqA== 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=aSdH6HfbA5HoEuR8Um/vA4vpzmNTgq6YCAyf5QR9FTc=; b=smGSfVgmzuwYHJI5aSpHC0x5fvOyteZeHyUQgma8BNLyOrhxru+kNhh+gYXZRiuUpi iohzoVJHTevvXgjezdbAd/SstSQLA4gI36QeJEuu6lL+YBS0kkWFmW2a3w5CTuPmPli2 N20wY+pvJJNK16AWmq1g0CgbfaCGO9Gd6CHQunl6Xb3g5TJZwVS+oXBVZy48EgCjWAws y+TebQ1dS5LobqPwC6EkSoLkMZcr4jUhsrA5Se235umu8bX89xeC3ALXQuZYMODNdgLG dmLzQacm/YTtnKg/CYxBdjiDETkfMSe7T3Fe2WFT8CTkIuvlByW/nuTRBKfoB3E9mcQl Q45Q== 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 a21-v6si3042580plm.211.2018.07.18.05.06.45; Wed, 18 Jul 2018 05:07:00 -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 S1727131AbeGRMnJ (ORCPT + 99 others); Wed, 18 Jul 2018 08:43:09 -0400 Received: from mx2.suse.de ([195.135.220.15]:49492 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726427AbeGRMnI (ORCPT ); Wed, 18 Jul 2018 08:43:08 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id A8E1FADCA; Wed, 18 Jul 2018 12:05:31 +0000 (UTC) Date: Wed, 18 Jul 2018 14:05:29 +0200 From: Michal Hocko To: Dan Williams Cc: pasha.tatashin@oracle.com, dalias@libc.org, Jan Kara , Benjamin Herrenschmidt , Heiko Carstens , linux-mm , Paul Mackerras , "H. Peter Anvin" , Yoshinori Sato , "linux-nvdimm@lists.01.org" , the arch/x86 maintainers , Matthew Wilcox , daniel.m.jordan@oracle.com, Ingo Molnar , fenghua.yu@intel.com, Jerome Glisse , Thomas Gleixner , "Luck, Tony" , Linux Kernel Mailing List , Michael Ellerman , Martin Schwidefsky , Andrew Morton , Christoph Hellwig Subject: Re: [PATCH v2 00/14] mm: Asynchronous + multithreaded memmap init for ZONE_DEVICE Message-ID: <20180718120529.GY7193@dhcp22.suse.cz> References: <153176041838.12695.3365448145295112857.stgit@dwillia2-desk3.amr.corp.intel.com> <20180717155006.GL7193@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue 17-07-18 10:32:32, Dan Williams wrote: > On Tue, Jul 17, 2018 at 8:50 AM Michal Hocko wrote: [...] > > Is there any reason that this work has to target the next merge window? > > The changelog is not really specific about that. > > Same reason as any other change in this space, hardware availability > continues to increase. These patches are a direct response to end user > reports of unacceptable init latency with current kernels. Do you have any reference please? > > There no numbers or > > anything that would make this sound as a high priority stuff. > > >From the end of the cover letter: > > "With this change an 8 socket system was observed to initialize pmem > namespaces in ~4 seconds whereas it was previously taking ~4 minutes." Well, yeah, it sounds like a nice to have thing to me. 4 minutes doesn't sounds excesive for a single init time operation. Machines are booting tens of minutes these days... > My plan if this is merged would be to come back and refactor it with > the deferred_init_memmap() implementation, my plan if this is not > merged would be to come back and refactor it with the > deferred_init_memmap() implementation. Well, my experience tells me that "refactor later" is rarely done. Especially when it is not critical thing to do. There are so many other things to go in the way to put that into back burner... So unless this is abslutely critical to have fixed in the upcoming merge window then I would much rather see a (reasonably) good solution from the begining. -- Michal Hocko SUSE Labs