From: Nicholas Mc Guire <der.herr@hofr.at>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: How is the size of init ram disk determined when initramfs is used?
Date: Sun, 1 Jan 2023 20:23:23 +0100 [thread overview]
Message-ID: <20230101192323.GA23315@osadl.at> (raw)
In-Reply-To: <a32c1bfa-7ded-59a7-8614-5817371b89a4@petrovitsch.priv.at>
On Sun, Jan 01, 2023 at 06:32:55PM +0100, Bernd Petrovitsch wrote:
> Hi all!
>
> On 07/10/2022 04:32, Chan Kim wrote:
> [...]
> >I'm using initramfs.cpio.gz for initial file system image.
> >I embed it in the kernel Image file.
> >After linux boots, when I'm in the shell, I can create files.
> >But I'm curious how much the file system can grow.
>
> Why not just try it once;-)
ramdisks are static - so if you mount ram0 and ramdisk_size=8192
then your ramdisk is occupying 8MB and that will be the hard limit
at least on some architectures (x86, I think also arm).
>
> >I remember somewhere reading that the initramdisk is made and the initramfs
> >archive is extracted in the ramdisk.
On some architectures you can pass the size as kernel parameter
ramdisk_size=#kb and that will then set the size of the ramdisk
when you mount it (at boot or during normaal operations).
As I did not find what archtiecture you are refering to this might
help - grep for ramdisk_size in Documentations and you should have
it. E.g. for arm it is marked as obsolete (arm/boot.rst) but still
seems to be supported with CONFIG_DEPRECATED_PARAM_STRUCT set.
Wonder what it is being replaced by.
thx!
hofrat
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2023-01-01 19:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 2:32 How is the size of init ram disk determined when initramfs is used? Chan Kim
2023-01-01 16:54 ` Richard
2023-01-01 17:32 ` Bernd Petrovitsch
2023-01-01 19:23 ` Nicholas Mc Guire [this message]
2023-01-02 2:37 ` Chan Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230101192323.GA23315@osadl.at \
--to=der.herr@hofr.at \
--cc=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).