From: "Jörn Engel" <joern@logfs.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: Jeff S <jsolman33@yahoo.com>, Josh Boyer <jwboyer@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: JFFS2 determine writing state
Date: Tue, 15 Jan 2008 17:50:43 +0100 [thread overview]
Message-ID: <20080115165043.GD22338@lazybastard.org> (raw)
In-Reply-To: <20080115140759.GE11941@shareable.org>
On Tue, 15 January 2008 14:08:00 +0000, Jamie Lokier wrote:
>
> But the particular fs behaviour is relevant the other way around: I
> have a program which calls open/write/close with small writes
> moderately often (because it calls another program which actually
> operates on the file).
>
> If JFFS2 commits pending writes on every close, I should change things
> to keep the file open between writes so they are coalesced and faster,
> when I don't need the individual writes to be committed separately.
JFFS2 also commits on every write. So you need userspace caching if you
want to coalesce things. fwrite might be enough for that...
> When I do need the data committed I can use fsync of course.
...as long as you also fflush (or fclose) before fsync.
Jörn
--
Everything should be made as simple as possible, but not simpler.
-- Albert Einstein
next prev parent reply other threads:[~2008-01-15 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 23:38 JFFS2 determine writing state Jeff S
2008-01-11 13:57 ` Josh Boyer
2008-01-12 10:03 ` Jamie Lokier
2008-01-12 20:15 ` Josh Boyer
2008-01-15 14:08 ` Jamie Lokier
2008-01-15 16:50 ` Jörn Engel [this message]
2008-01-15 17:35 ` Jamie Lokier
2008-01-15 19:16 ` Jörn Engel
2008-01-15 21:51 ` Jamie Lokier
2008-01-15 23:26 ` 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=20080115165043.GD22338@lazybastard.org \
--to=joern@logfs.org \
--cc=jamie@shareable.org \
--cc=jsolman33@yahoo.com \
--cc=jwboyer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox