[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170814113445.GE19063@dhcp22.suse.cz>
Date: Mon, 14 Aug 2017 13:34:45 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Pasha Tatashin <pasha.tatashin@...cle.com>
Cc: linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
x86@...nel.org, kasan-dev@...glegroups.com, borntraeger@...ibm.com,
heiko.carstens@...ibm.com, davem@...emloft.net,
willy@...radead.org, ard.biesheuvel@...aro.org,
will.deacon@....com, catalin.marinas@....com, sam@...nborg.org,
Mel Gorman <mgorman@...e.de>
Subject: Re: [v6 04/15] mm: discard memblock data later
On Fri 11-08-17 15:00:47, Pasha Tatashin wrote:
> Hi Michal,
>
> This suggestion won't work, because there are arches without memblock
> support: tile, sh...
>
> So, I would still need to have:
>
> #ifdef CONFIG_MEMBLOCK in page_alloc, or define memblock_discard() stubs in
> nobootmem headfile.
This is the standard way to do this. And it is usually preferred to
proliferate ifdefs in the code.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists