From: Esben Nielsen <esn@cotas.dk>
To: tglx@linutronix.de, "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Jasmine Strong" <jasmine@regolith.co.uk>
Cc: Holger Schurig <h.schurig@mn-logistik.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Database on JFFS2?
Date: Tue, 22 Apr 2003 10:07:59 +0200 [thread overview]
Message-ID: <200304221007.59780.esn@cotas.dk> (raw)
In-Reply-To: <200304161335.50367.tglx@linutronix.de>
On Wednesday 16 April 2003 13:35, Thomas Gleixner wrote:
> [...]
> On Wednesday 16 April 2003 12:04, Esben Nielsen wrote:
> > I am not much into flash technology itself (NOR contra NAND), but I know
> > that on our device one write erases and rewrites one block of 128k. Each
> > block can only be erased between 1E5 and 1E6 times. We thus have to be
> > carefull as our device have to live for 20 years (yes, that is what a
> > promise our customers!).
>
> Erase is always a full block (e.g. 128K), but writes happen in small
> chunks.
>
Ah! Now I get it: You have erase a block as a whole and then you can write
parts of it until it is full? I always believed you had to write a full block
just to write a single byte, but this does make much more sense to me. We
have been through similar discussions with TFFS under vxWorks where we
couldn't find out how many times we were actually allowed to write.
> [...]
>
> JFSS2 does no write on fsync, as data are already written.
Doesn't Linux per default for any filesystem hold a write cache which needs to
be flushed with fsync()?
Esben
next prev parent reply other threads:[~2003-04-22 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030415171123.GH7721@wohnheim.fh-wedel.de>
2003-04-16 10:04 ` Database on JFFS2? Esben Nielsen
2003-04-16 11:35 ` Thomas Gleixner
2003-04-16 11:13 ` Jörn Engel
2003-04-16 14:05 ` Thomas Gleixner
2003-04-16 13:08 ` Jörn Engel
2003-04-16 14:30 ` matsunaga
2003-04-16 18:19 ` Thomas Gleixner
2003-04-17 16:02 ` matsunaga
2003-04-22 8:07 ` Esben Nielsen [this message]
2003-04-22 8:24 ` Jörn Engel
[not found] <00512BA4F9D3D311912A009027E9B8F407E4D9@NT>
2003-04-16 15:23 ` Jörn Engel
2003-04-14 8:08 Esben Nielsen
2003-04-14 23:03 ` Charles Manning
2003-04-15 8:06 ` Esben Nielsen
2003-04-15 8:51 ` Holger Schurig
2003-04-15 15:06 ` Esben Nielsen
2003-04-15 15:39 ` Jörn Engel
2003-04-15 16:11 ` Jasmine Strong
2003-04-15 16:14 ` Jörn Engel
2003-04-15 16:23 ` Jasmine Strong
2003-04-16 11:16 ` Jörn Engel
2003-04-15 9:13 ` Jörn Engel
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=200304221007.59780.esn@cotas.dk \
--to=esn@cotas.dk \
--cc=h.schurig@mn-logistik.de \
--cc=jasmine@regolith.co.uk \
--cc=joern@wohnheim.fh-wedel.de \
--cc=tglx@linutronix.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