From: David Woodhouse <dwmw2@infradead.org>
To: Sergei Sharonov <sergei.sharonov@halliburton.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2 and frequent/small write operations
Date: Mon, 04 Apr 2005 19:55:33 +0100 [thread overview]
Message-ID: <1112640934.24487.375.camel@hades.cambridge.redhat.com> (raw)
In-Reply-To: <loom.20050404T173154-376@post.gmane.org>
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.
This has nothing to do with atomicity of writes with respect to power
failure.
--
dwmw2
next prev parent reply other threads:[~2005-04-04 18:55 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 [this message]
2005-04-04 21:08 ` Sergei Sharonov
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=1112640934.24487.375.camel@hades.cambridge.redhat.com \
--to=dwmw2@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox