From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Alex Pavloff <apavloff@eason.com>
Cc: "'Tobias Otto-Adamczak'" <toa@indakom.de>, linux-mtd@lists.infradead.org
Subject: Re: writing new BBRAM driver
Date: Tue, 17 Dec 2002 10:12:27 +0100 [thread overview]
Message-ID: <20021217091227.GA11194@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <D3AF5F134D627243993F2F2FC32EE4D229C4B0@mailman.eason.com>
On Mon, 16 December 2002 14:33:41 -0800, Alex Pavloff wrote:
>
> Alright, one more question: What should the erasesize be for BBRAM?
> Obviously I'm not worried about wear, so should it be zero or one or
> something else?
Depends. :-)
For jffs2, you need 5 free blocks for operation. But every used block
eats up ~150Byte roughly, depending on data and compression. Bigger
blocks eat memory, more blocks eat memory, minimum is somewhere in the
middle, you do the math.
For minix, fat, ext2/3 etc., this doesn't really matter. I'd pick 4k,
as that is pagesize on most machines, but even 1byte might work - with
lots of overhead.
Jörn
--
But this is not to say that the main benefit of Linux and other GPL
software is lower-cost. Control is the main benefit--cost is secondary.
-- Bruce Perens
next prev parent reply other threads:[~2002-12-17 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 22:33 writing new BBRAM driver Alex Pavloff
2002-12-17 9:12 ` Jörn Engel [this message]
2002-12-17 9:49 ` Tobias Otto-Adamczak
-- strict thread matches above, loose matches on Subject: below --
2002-12-20 1:14 Alex Pavloff
2002-12-13 23:45 Alex Pavloff
2002-12-16 10:14 ` Tobias Otto-Adamczak
2002-12-16 12:54 ` Geoffroy Stevenne
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=20021217091227.GA11194@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=apavloff@eason.com \
--cc=linux-mtd@lists.infradead.org \
--cc=toa@indakom.de \
/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