From: Nathan Lynch <ntl@pobox.com>
To: Ran Shalit <ranshalit@gmail.com>
Cc: "Ricard Wanderlöf" <ricardw@axis.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Q: Cramfs Vs. Ubifs
Date: Wed, 13 Jun 2012 10:46:20 -0500 [thread overview]
Message-ID: <1339602380.32578.4.camel@doorstop.aus.2wire.com> (raw)
In-Reply-To: <CAJ2oMhKGbvN5E9R_Ybw4OCDVtFq6sqhZ+R0qx68A_SzSLW-x5A@mail.gmail.com>
On Wed, 2012-06-13 at 18:25 +0300, Ran Shalit wrote:
> > Even if you copy all files to a RAM-based file system, such as /tmp, they
> > still need to be copied from the file system to directly accessible memory
> > before execution. While it may be faster than performing the same operation
> > from flash, the demand paging functionality is still in operation.
> >
> > The only way to avoid it would be to force loading of all pages for a
> > program at its start, I've never had the need so I don't know how though.
> >
> >
> Yes, that what I meant. At the initialization stage we will copy all
> files from ubifs section into root file system in RAM and so I assume
> that there will be no any access to flash during application life for
> read or write (any desired access will be controlled by application).
> I wonder why I didn't find any information about disadvantage of using
> ubifs as root file system in embedded system in terms of access to
> flash during application life.
This isn't an issue specific to UBIFS. Look into mlock/mlockall if your
application needs to avoid latencies associated with demand-paging from
flash or any other storage.
next prev parent reply other threads:[~2012-06-13 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 19:17 Q: Cramfs Vs. Ubifs Ran Shalit
2012-06-05 8:33 ` Ricard Wanderlof
[not found] ` <CAJ2oMhK0isouNBTzMEXPvRLAjFFcSCzWn_gvszrgt1_6Nvw13A@mail.gmail.com>
2012-06-05 9:29 ` Ricard Wanderlof
2012-06-06 19:08 ` Thomas Petazzoni
2012-06-12 4:54 ` Ran Shalit
2012-06-13 6:55 ` Ricard Wanderlof
2012-06-13 14:26 ` Ran Shalit
2012-06-13 14:59 ` Ricard Wanderlof
2012-06-13 15:25 ` Ran Shalit
2012-06-13 15:32 ` Ricard Wanderlof
2012-06-13 15:46 ` Nathan Lynch [this message]
2012-06-14 5:37 ` Ran Shalit
2012-06-14 6:23 ` Nathan Lynch
2012-06-14 6:57 ` Ricard Wanderlof
2012-06-06 19:11 ` 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=1339602380.32578.4.camel@doorstop.aus.2wire.com \
--to=ntl@pobox.com \
--cc=linux-mtd@lists.infradead.org \
--cc=ranshalit@gmail.com \
--cc=ricardw@axis.com \
/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