From: David Woodhouse <dwmw2@infradead.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: R&D4 <r&d4@dave-tech.it>, "Jörn Engel" <joern@lazybastard.org>,
mtd_mailinglist <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2 as transactional FS (in other words: how to be sure that data have been writtent correctly from userspace)
Date: Thu, 08 Mar 2007 13:58:25 +0000 [thread overview]
Message-ID: <1173362305.3461.447.camel@pmac.infradead.org> (raw)
In-Reply-To: <1173361473.4861.12.camel@zod.rchland.ibm.com>
On Thu, 2007-03-08 at 07:44 -0600, Josh Boyer wrote:
> Wait... why? Rejecting mount -o sync seems sane, but why can't O_SYNC
> support be handled? If users want to open their files like that and it
> causes JFFS2 to flush a bunch of padding out, well they asked for it.
Users ask for shared writable mmap too. That isn't a good idea either.
Contemplate what Linus always says about using 'volatile' vs. proper
barriers. Now consider it for O_SYNC vs. fsync(). And factor in the fact
that O_SYNC is going to be massively suboptimal if it causes syncs when
they otherwise didn't need to happen.
--
dwmw2
next prev parent reply other threads:[~2007-03-08 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 9:49 JFFS2 as transactional FS (in other words: how to be sure that data have been writtent correctly from userspace) R&D4
2007-03-08 10:51 ` David Woodhouse
2007-03-08 12:54 ` Jörn Engel
2007-03-08 13:04 ` David Woodhouse
2007-03-08 13:12 ` Jörn Engel
2007-03-08 13:22 ` David Woodhouse
2007-03-08 13:44 ` Josh Boyer
2007-03-08 13:58 ` David Woodhouse [this message]
2007-03-08 14:35 ` Josh Boyer
2007-03-08 14:43 ` Jörn Engel
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=1173362305.3461.447.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=joern@lazybastard.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
--cc=r&d4@dave-tech.it \
/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