All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Sharonov <sergei.sharonov@halliburton.com>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 and frequent/small write operations
Date: Mon, 4 Apr 2005 21:08:35 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050404T224215-1@post.gmane.org> (raw)
In-Reply-To: 1112640934.24487.375.camel@hades.cambridge.redhat.com

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?
 
> This has nothing to do with atomicity of writes with respect to power
> failure.

Sorry for the confusion. I did not mean that O_SYNC has anything to do 
with atomicity, only that it is usually one of the ways to assure that
all the data is flushed to media. I guess I heard that O_SYNC does
not work with JFFS2, did not want to accept it and was provoking people 
to confirm or disprove it ;-)

Sergei Sharonov

  reply	other threads:[~2005-04-04 21:13 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 [this message]
2005-04-05  8:43       ` Estelle HAMMACHE
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=loom.20050404T224215-1@post.gmane.org \
    --to=sergei.sharonov@halliburton.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 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.