From: Ted Ts'o <tytso@mit.edu>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 on 32GB SD card.
Date: Fri, 11 Nov 2011 20:20:19 -0500 [thread overview]
Message-ID: <20111112012019.GB4055@thunk.org> (raw)
In-Reply-To: <CAAMvbhF2tBWZduzZFx_sp_V2YVssPjTqVJROyTHnpLBDJ1XK9g@mail.gmail.com>
On Fri, Nov 11, 2011 at 12:31:19PM +0000, James Courtier-Dutton wrote:
>
> I wish to use an SD card in an embedded device use the ext4 filesystem on it.
> How much RAM would ext4 need to support this?
> I am assuming ext4 holds some sort of allocation table/metadata in RAM.
The minimum amount of space which ext4 keeps pinned in memory for a
32G file system is 3 4k blocks, plus an in-core memory. If you
include things like the root directory that always have to be there,
we're talking maybe 24k or so. Of course, the moment you actually
*do* something with the file system more metadata will get paged in,
and if you are running with very little memory, blocks will get pushed
out of memory, and then will have to read back into memory, and things
like delayed allocation won't work as well.
So you have to distinguish between "the bare minimum so you can mount
a file system", and "what you need so that you have acceptably good
performance for your workload" --- and that's going to be very
dependent on your workload.
Also, note that with performance, it's highly dependant on the SD
card; some SD cards are crap, and only support one write window at a
time, and others may support 8 or more write windows.
The other question is making sure you have enough memory so that you
can run e2fsck on a 32GB file system.
In general, the best thing to do is to try it, and see if it works.
Regards,
- Ted
next prev parent reply other threads:[~2011-11-12 5:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 12:31 ext4 on 32GB SD card James Courtier-Dutton
2011-11-12 1:20 ` Ted Ts'o [this message]
2011-11-12 5:31 ` Andreas Dilger
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=20111112012019.GB4055@thunk.org \
--to=tytso@mit.edu \
--cc=james.dutton@gmail.com \
--cc=linux-ext4@vger.kernel.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