From: Jamie Lokier <jamie@shareable.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-mtd@lists.infradead.org, Josh Boyer <jwboyer@gmail.com>,
David Woodhouse <dwmw2@infradead.org>, Duke <ezbonites@gmail.com>
Subject: Re: jffs2: too few erase blocks
Date: Mon, 29 Oct 2007 20:51:25 +0000 [thread overview]
Message-ID: <20071029205125.GA27773@mail.shareable.org> (raw)
In-Reply-To: <20071029143818.GA29885@lazybastard.org>
Jörn Engel wrote:
> On Sun, 28 October 2007 22:59:07 -0400, David Woodhouse wrote:
> >
> > Yes, it does. In fact, on NOR flash you get entirely synchronous
> > behaviour even _without_ explicit syncs -- effectively the same as
> > MS_SYNC.
>
> On older ones. There appears to be a tendency for newer flashes to
> require wbuf and hence sync.
When you say "sync", do fdatasync() / fsync() on open files and
directories flush the necessary blocks from wbuf for those
files/directories data and their inode metadata, for JFFS2?
I have been calling sync(), but I wonder if fdatasync/fsync do as they
are supposed to?
(If you know about other fses like LogFS/Yaffs/UBIFS that would be
handy, too).
Probably all are unnecessary in my specific application, as I use a
JFFS2 with cfi_cmdset_0002, which I get the impression doesn't buffer
any writes anyway. But I like to get the application code right, in
case I change to another device.
-- Jamie
next prev parent reply other threads:[~2007-10-29 21:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:06 jffs2: too few erase blocks Duke
2007-10-25 14:22 ` Josh Boyer
2007-10-25 22:15 ` Jamie Lokier
2007-10-26 17:00 ` Duke
2007-10-26 21:02 ` Duke
2007-10-28 18:02 ` Jamie Lokier
2007-10-29 2:59 ` David Woodhouse
2007-10-29 14:38 ` Jörn Engel
2007-10-29 20:51 ` Jamie Lokier [this message]
2007-10-29 21:40 ` David Woodhouse
2007-10-29 22:50 ` Jamie Lokier
2007-10-29 21:54 ` Jörn Engel
2007-10-29 22:46 ` Jamie Lokier
2007-10-30 16:09 ` Jörn Engel
2007-10-30 20:08 ` Duke
2007-10-30 20:19 ` Jörn Engel
2007-10-30 21:42 ` Duke
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=20071029205125.GA27773@mail.shareable.org \
--to=jamie@shareable.org \
--cc=dwmw2@infradead.org \
--cc=ezbonites@gmail.com \
--cc=joern@logfs.org \
--cc=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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