public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: matsunaga <matsunaga_kazuhisa@yahoo.co.jp>,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org
Cc: Holger Schurig <h.schurig@mn-logistik.de>
Cc: esn@cotas.dk
Cc: Jasmine Strong <jasmine@regolith.co.uk>
Subject: Re: Database on JFFS2?
Date: Wed, 16 Apr 2003 20:19:50 +0200	[thread overview]
Message-ID: <200304162019.50838.tglx@linutronix.de> (raw)
In-Reply-To: <002501c30424$c3fedf20$a10486da@w0a3t0>

On Wednesday 16 April 2003 16:30, matsunaga wrote:
> > iirc it used to ignore sync completely so people could potentially get
> > into trouble if they write-sync-poweroff with <2s between write and
> > poweroff.
>
> write - sync -poweroff works on NAND. flush_wbuf is also triggered on
> umount.
>
> I think that sys_sync is not supported yet, as is written in jffs2/Todo,
> right?

Sorry, I mixed this up with fsync. sys_sync is not working, just flushing the 
buffer on umount.

When I brought in the timed flush, I tried to use kupdated 
(superblock->s_dirty) and had a bunch of unwanted flush's during consecutive 
writes, because setting sb->s_dirty is asynchronous to kupdated interval.  
That's why I used the 2 seconds timer. 

I will think about it again.

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2003-04-16 17:20 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 [this message]
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
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=200304162019.50838.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matsunaga_kazuhisa@yahoo.co.jp \
    /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