From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] First rootfile system build using buildroot
Date: Tue, 1 Sep 2015 08:56:38 +0200 [thread overview]
Message-ID: <20150901085638.774989e3@free-electrons.com> (raw)
In-Reply-To: <944894A3EB1D044A9003B2F944389BB20474C3452F@svr-wa-exch1.atg.lc>
Hello,
On Mon, 31 Aug 2015 13:58:04 -0700, Lee, Tommy wrote:
> Building the rootfilesystem into zImage resolves the rootfilesystem
> loading/linking issue clearly. I do not see any reason to build and
> load the rootfilesystem independently.
If by "building the root filesystem into zImage" you mean using the
initramfs mechanism, then clearly there is a reason to have the root
filesystem independently.
The initramfs mechanism is OK when the filesystem is relatively small.
When it starts to be bigger, then initramfs has a number of drawbacks:
* The entire root filesystem must be loaded at boot time. If you have
a 5 or 6 MB root filesystem, that's probably alright. But if you
have a 100-200 MB root filesystem, then it's going to take a while.
By using a normal root filesystem, it gets mounted at boot time, but
not its entire contents are loaded into memory at boot time.
* The entire root filesystem will always be in memory, consuming this
memory. Again if your filesystem is 5, 6, 8 or 16 MB, this might be
alright. But if your filesystem is 100-200 MB, you probably don't
want those 100-200 MB to be permanently loaded into memory.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-01 6:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 14:37 [Buildroot] First rootfile system build using buildroot Dinesh Guleria
2015-08-31 15:18 ` Dinesh Guleria
2015-08-31 15:53 ` Lee, Tommy
2015-08-31 17:17 ` Dinesh Guleria
2015-08-31 20:58 ` Lee, Tommy
2015-09-01 1:09 ` Dinesh Guleria
2015-09-01 6:58 ` Thomas Petazzoni
2015-09-01 11:25 ` Dinesh Guleria
2015-09-01 12:02 ` Dinesh Guleria
2015-09-01 12:14 ` Vicente Olivert Riera
2015-09-01 13:23 ` Dinesh Guleria
2015-09-01 15:54 ` Lee, Tommy
2015-09-01 15:57 ` Lee, Tommy
[not found] ` <CAKpDV8uny8GAJrEkEBmMdcboOrGuVQ4G09KRtL9yuvgH1XKE=Q@mail.gmail.com>
2015-09-01 17:45 ` Lee, Tommy
2015-09-02 0:29 ` Dinesh Guleria
2015-09-02 3:38 ` Baruch Siach
2015-09-02 11:06 ` Dinesh Guleria
2015-09-02 11:47 ` Baruch Siach
2015-09-02 13:54 ` Dinesh Guleria
2015-09-02 13:59 ` Vicente Olivert Riera
2015-09-02 14:51 ` Dinesh Guleria
2015-09-02 14:55 ` Vicente Olivert Riera
2015-09-02 16:57 ` Dinesh Guleria
2015-09-02 17:16 ` Baruch Siach
2015-09-02 17:58 ` Dinesh Guleria
2015-09-02 18:13 ` Dinesh Guleria
2015-09-02 18:24 ` Samuel Martin
2015-09-01 6:56 ` Thomas Petazzoni [this message]
2015-08-31 20:45 ` Thomas Petazzoni
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=20150901085638.774989e3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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