From: "Grant Edwards" <grante@visi.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: ecos-discuss@sources.redhat.com
Subject: [ECOS] Re: Simple flash filesystem?
Date: Tue, 06 Feb 2001 13:03:00 -0000 [thread overview]
Message-ID: <20010206210322.BF3EE7A814@visi.com> (raw)
In-Reply-To: <4.3.2.7.2.20010206154319.00b19870@larwe.com>
Lewin A.R.W. Edwards writes:
> >way too big/complex when my filesystem isn't going to be more than a few
> >hundred KBytes and will be rarely written to. For now, I'm going to try
>
> Aha!! Do you have a "few hundred KBytes" of free RAM?
I should.
> You could get the best of all possible worlds by loading the FS into RAM,
> and allowing random R/W as convenient, then committing the entire thing
> back to flash when your device is idle.
Yup.
That's probably the simplest solution for a small filesystem. Burns can
happen in the background without interrupting read access to the RAM
version of the files.
Of course once marketing gets hold of the web pages, I may end up with
several megabytes of real-audio and dancing GIFs. Then half of my
assumptions go out the window. :)
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-02-06 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <981465384.28425.ezmlm@sources.redhat.com>
2001-02-06 12:30 ` Kristian Otnes
2001-02-06 12:50 ` Grant Edwards
2001-02-06 12:54 ` Lewin A.R.W. Edwards
2001-02-06 13:03 ` Grant Edwards [this message]
2001-02-06 13:13 ` [ECOS] Touch screen on EP7211 Wilson Kwan
2001-02-07 5:07 ` Lewin A.R.W. Edwards
2001-02-07 8:12 ` Wilson Kwan
2001-02-05 14:29 [ECOS] Simple flash filesystem? Lewin A.R.W. Edwards
2001-02-06 8:05 ` [ECOS] " Grant Edwards
2001-02-06 8:21 ` Lewin A.R.W. Edwards
2001-02-06 8:43 ` Grant Edwards
2001-02-06 9:20 ` Wilson Kwan
2001-02-06 9:28 ` Grant Edwards
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=20010206210322.BF3EE7A814@visi.com \
--to=grante@visi.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=larwe@larwe.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).