Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp3942083imm; Mon, 25 Jun 2018 07:11:49 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKUzmwwq0WzWmYgpIN2pvtGHh0bkPlBcPWEQcf/37U00sdQMsKbLBi6gqeX+hZ5syVLLkeS X-Received: by 2002:a17:902:788e:: with SMTP id q14-v6mr12507841pll.234.1529935909126; Mon, 25 Jun 2018 07:11:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529935909; cv=none; d=google.com; s=arc-20160816; b=0JyGHVnY7f/38Y6rsvfNM2y6wfd3wY2i80rmYMavR7Zetvdja1exR22TVNqGUWW0FV 6cY+hOYUOk5oSJ8+W7ob1DcQfzk6QvsvPS9wX4uW7oqxNM+TclSSZea9hYbtB4gcus7t nsicVrMtAOg1e3mBu13VxOgNyvYIAjZ0EkZaigSEAs39vFD9uFHMfePmLddyE2fVD6Eo knncPqFY8TV7xkLoo66EMCjOxF2QOGVmcGRSst77g4ZWznX+wYol7Agm5cS2Vmp/RT7u DQM+rlEhPScUUl444ASb0ve9zdzxkmrgYnUSWzMsYgnZXNKTblCBa+/6IlHcRsswk+9Q BG2A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date :arc-authentication-results; bh=bc0ZvJNpGP2urPseJnTPf2f2QB3wzwQcJMbM3r3azxE=; b=I1o2dyujhmsNI6zKMWOQPH464lZpE+mHZhtl27xmRiIYVQ+Dv7vyFc0Sk4CEcd/rHn cOSCirLWcjrV1CRjr2nIAZqpGY4Nbc+oyqU13VnLOjMMFjl2WCC/K3W+EOxWmVkaBKb8 HqhqhEINaFxdct4e4ssPzazaZnnKeSK50idJA4btNW3hGXRfbNmL8DlTLxM81m8YUtFA gI3cmWgY6IbHP0T9rOSbvMnXs7P8YxVf0gPVF+JaQ9diHrwqGMc6c+4Ik4za61i0bmaM YYIlL/6Ke+KIg6H3a1DkKip9aM899wxvyXFDLu80TBe6Qx63MnjSwQQmQs/089b/HvmV d6fw== 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 z3-v6si13647029plb.246.2018.06.25.07.11.34; Mon, 25 Jun 2018 07:11:49 -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 S934389AbeFYOH6 (ORCPT + 99 others); Mon, 25 Jun 2018 10:07:58 -0400 Received: from mx2.suse.de ([195.135.220.15]:54005 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934329AbeFYOH4 (ORCPT ); Mon, 25 Jun 2018 10:07:56 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 0E50BADCC; Mon, 25 Jun 2018 14:07:54 +0000 (UTC) Date: Mon, 25 Jun 2018 16:07:54 +0200 From: Michal Hocko To: linux-mm@kvack.org Cc: Johannes Weiner , Andrew Morton , linux-arch@vger.kernel.org, LKML Subject: why do we still need bootmem allocator? Message-ID: <20180625140754.GB29102@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I am wondering why do we still keep mm/bootmem.c when most architectures already moved to nobootmem. Is there any fundamental reason why others cannot or this is just a matter of work? Btw. what really needs to be done? Btw. is there any documentation telling us what needs to be done in that regards? -- Michal Hocko SUSE Labs