From: Estelle HAMMACHE <estelle.hammache@st.com>
To: Sergei Sharonov <sergei.sharonov@halliburton.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 and frequent/small write operations
Date: Tue, 05 Apr 2005 10:43:41 +0200 [thread overview]
Message-ID: <42524FBD.C418A0E6@st.com> (raw)
In-Reply-To: loom.20050404T224215-1@post.gmane.org
Hi Sergei,
Sergei Sharonov wrote:
>
> Hi,
> > On Mon, 2005-04-04 at 17:15 +0000, Sergei Sharonov wrote:
> > > I was told that O_SYNC flag for open does not work with JFFS2 (!?).
> >
> > You misunderstood. On NOR flash, O_SYNC does nothing because JFFS2 is
> > entirely synchronous anyway. On NAND flash, I believe that O_SYNC does
> > what it is supposed to -- any write will have reached the medium before
> > the write() system call returns.
>
> Thanks, that is good to know. It was suggested by others
> http://article.gmane.org/gmane.linux.drivers.mtd/12175/match=+sync
> that it may not work on JFFS2. Estelle?
In the quoted message it was pretty clear that I don't know
one way or another (don't use linux VFS).
I was referring to previous discussions such as
"jffs2_get_inode_nodes(): Data CRC failed on NAND device" in the
February archive, where O_SYNC is _not_ proposed as a solution
to force fsync.
Sorry for the confusion... I'm glad this erroneous notion
is corrected.
bye
Estelle
next prev parent reply other threads:[~2005-04-05 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 13:58 JFFS2 and frequent/small write operations Gianluca Moro
2005-04-04 17:15 ` Sergei Sharonov
2005-04-04 18:55 ` David Woodhouse
2005-04-04 21:08 ` Sergei Sharonov
2005-04-05 8:43 ` Estelle HAMMACHE [this message]
2005-04-05 9:27 ` David Woodhouse
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=42524FBD.C418A0E6@st.com \
--to=estelle.hammache@st.com \
--cc=linux-mtd@lists.infradead.org \
--cc=sergei.sharonov@halliburton.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.