public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Esben Nielsen <esn@cotas.dk>
Cc: manningc2@actrix.gen.nz
Cc: linux-mtd@lists.infradead.org
Subject: Re: Database on JFFS2?
Date: Tue, 15 Apr 2003 11:13:07 +0200	[thread overview]
Message-ID: <20030415091306.GD10280@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <200304151006.51147.esn@cotas.dk>

On Tue, 15 April 2003 10:06:51 +0200, Esben Nielsen wrote:
> 
> Our flash is NOR (Intel statoflash). What we a going for is a standeard SQL 
> solution  - so it isn't enough that the filesystem has a database-like 
> behaviour.
> 
> Someone from this list pointed out sqlite to me yesterday. I am looking into 
> that now.  It has a log system. The most optimal would be if the database 
> could be tuned not to write too often and on other hand when it does it is 
> flush to flash immediately to prevent datacorruption. I am not quite sure how 
> to make it work with JFFS2. DoesJFFS2 write immediately on fsync() or it is 
> buffered in ram making the database believe it is safe to delete it's 
> transactionlog?

afaik jffs2 writes immediately to flash, even without fsync, as long
as you use NOR. NAND holds a buffer for 2s, I'd have to check when
this is flushed exactly.

Jörn

-- 
Those who come seeking peace without a treaty are plotting.
-- Sun Tzu

  parent reply	other threads:[~2003-04-15  9:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14  8:08 Database on JFFS2? 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 [this message]
     [not found] <20030415171123.GH7721@wohnheim.fh-wedel.de>
2003-04-16 10:04 ` 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
2003-04-22  8:24       ` Jörn Engel
     [not found] <00512BA4F9D3D311912A009027E9B8F407E4D9@NT>
2003-04-16 15:23 ` 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=20030415091306.GD10280@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=esn@cotas.dk \
    --cc=manningc2@actrix.gen.nz \
    /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