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=-2.5 required=3.0 tests=MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham 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 84564C43142 for ; Mon, 25 Jun 2018 18:03:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4A83520882 for ; Mon, 25 Jun 2018 18:03:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4A83520882 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964895AbeFYSD5 (ORCPT ); Mon, 25 Jun 2018 14:03:57 -0400 Received: from mx2.suse.de ([195.135.220.15]:48462 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934041AbeFYSDf (ORCPT ); Mon, 25 Jun 2018 14:03:35 -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 E0B14AB1E; Mon, 25 Jun 2018 18:03:33 +0000 (UTC) Date: Mon, 25 Jun 2018 20:03:32 +0200 From: Michal Hocko To: Rob Herring Cc: linux-mm@kvack.org, hannes@cmpxchg.org, Andrew Morton , linux-arch@vger.kernel.org, Linux Kernel Mailing List Subject: Re: why do we still need bootmem allocator? Message-ID: <20180625180332.GR28965@dhcp22.suse.cz> References: <20180625140754.GB29102@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Mon 25-06-18 10:09:41, Rob Herring wrote: > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko wrote: > > > > 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? > > Just because no one has done the work. I did a couple of arches > recently (sh, microblaze, and h8300) mainly because I broke them with > some DT changes. I see > > Btw. what really needs to be > > done? Btw. is there any documentation telling us what needs to be done > > in that regards? > > No. The commits converting the arches are the only documentation. It's > a bit more complicated for platforms that have NUMA support. I do not see why should be NUMA a problem but I will have a look at your commits to see what you have done. Thanks! -- Michal Hocko SUSE Labs