From: Brad Campbell <brad@wasp.net.au>
To: Patrick Hilt <philt@pioneer-pdt.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS 2 Question
Date: Sat, 10 Jul 2004 13:38:14 +0400 [thread overview]
Message-ID: <40EFB906.7060701@wasp.net.au> (raw)
In-Reply-To: <200407091608.14442.philt@pioneer-pdt.com>
Patrick Hilt wrote:
> Hi list!
> Is there a way to make sure data is being written to physical flash when using
> JFFS2? In other words, After writing a file on a JFFS2 partition, is there
> anything that can be done to make sure that the data is getting written to
> the flash right away? Would "sync" or "fsync" have that effect?
I believe that jffs2 is a synchronous filesystem in any case. By the time your application has
returned from the write() call, the data is on flash.
It certainly worked that way while I was debugging some software that did stupid things like write
800kb files 1 byte at a time.
Regards,
Brad
next prev parent reply other threads:[~2004-07-10 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-09 23:08 JFFS 2 Question Patrick Hilt
2004-07-10 9:31 ` Mike Wellington
2004-07-10 9:38 ` Brad Campbell [this message]
2004-07-10 10:18 ` Thomas Gleixner
2004-07-10 11:50 ` Wolfgang Denk
2004-07-15 16:47 ` Patrick Hilt
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=40EFB906.7060701@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-mtd@lists.infradead.org \
--cc=philt@pioneer-pdt.com \
/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