From: Charles Tilbury <charles.tilbury@comcast.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Artem B. Bityuckiy" <dedekind@yandex.ru>, linux-mtd@lists.infradead.org
Subject: Re: NAND flash question
Date: Tue, 28 Jun 2005 11:57:39 -0700 [thread overview]
Message-ID: <200506281157.39708.charles.tilbury@comcast.net> (raw)
In-Reply-To: <1119983460.12240.22.camel@hades.cambridge.redhat.com>
On Tuesday 28 June 2005 11:30 am, David Woodhouse wrote:
> On Tue, 2005-06-28 at 09:41 -0700, Charles Tilbury wrote:
> > In part, I want to get rid of the messages. They make the marketing
> > guys nervous. <<grin>> I may just supress them using comments. What
> > I really need is to make sure that the user land data gets flushed to
> > NAND before power loss. That seems like a JFFS2 issue, do you agree?
>
> Not really. Userland data are flushed to the medium on fsync() or sync()
> just as with other file systems. If a write() call has _just finished
> when the power is lost, there's no guarantee that _any_ file system will
> have committed that write to the medium already. (Unless you were using
> O_SYNC, which we don't support for JFFS2).
How could one change the flush interval to around 100mS? Or does that sound
like a stupid idea?
next prev parent reply other threads:[~2005-06-28 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 21:09 NAND flash question Charles Tilbury
2005-06-27 21:57 ` Sergei Sharonov
2005-06-28 7:23 ` Artem B. Bityuckiy
2005-06-28 15:58 ` Charles Tilbury
2005-06-28 16:06 ` Artem B. Bityuckiy
2005-06-28 16:41 ` Charles Tilbury
2005-06-28 18:30 ` David Woodhouse
2005-06-28 18:57 ` Charles Tilbury [this message]
2005-06-28 19:20 ` Sergei Sharonov
2005-06-29 6:39 ` Artem B. Bityuckiy
2005-06-29 6:29 ` Artem B. Bityuckiy
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=200506281157.39708.charles.tilbury@comcast.net \
--to=charles.tilbury@comcast.net \
--cc=dedekind@yandex.ru \
--cc=dwmw2@infradead.org \
--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