* Shea Levy wrote:
> > Please also put it into Documentation/features/.
>
> I switched this patch series (the latest revision v6 was just posted) to
> using weak symbols instead of Kconfig. Does it still warrant documentation?
Probably not.
Thanks,
Ingo
_
> The default limit of only 65536 VMAs will also quickly come into play
> if consecutive anon mmaps don't get merged. Of course this can be
> raised, but it has significant resource and performance (fork) costs.
Could the random mmap address chooser look for how many existing
VMAs have space befor
Hi Ingo,
Ingo Molnar writes:
> * Shea Levy wrote:
>
>> Now only those architectures that have custom initrd free requirements
>> need to define free_initrd_mem.
>>
>> Signed-off-by: Shea Levy
>
> Please put the Kconfig symbol name this patch introduces both into the title,
> so
> that peopl
The first patch in this series added a weakly-defined generic
implementation, which is functionally identical to the
architecture-specific one removed here.
Series boot-tested on RISC-V (which now uses the generic
implementation) and x86_64 (which doesn't).
Signed-off-by: Shea Levy
---
arch/arc
