linux-kernel - Re: increasing memory alloted for 'init' during kernel boot.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 31 Aug 2010 10:22:20 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Prabhu Chawandi <prabhu.chavandi@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-mips@...r.kernel.org
Subject: Re: increasing memory alloted for 'init' during kernel boot.

On 08/31/2010 08:49 AM, Prabhu Chawandi wrote:
> Hi all,
> 
>    Whenever the kernel starts booting, I am getting the bellow log :
> 
> Memory: 110080k/262144k available (2566k kernel code, 151952k
> reserved, 561k data, 15328k init, 0k highmem).
> 
> For 'init' on what bases this amount of memory is decided ?
> 
> Anyways I can alter it?

Nope. It's code and data inside .init, .exit and similar sections. Those
are marked by __init, __exit etc. in the code. This memory is freed
after the kernel is up and running, since this memory (code and data) is
not needed anymore.

regards,
-- 
js
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/