From: "Jörn Engel" <joern@logfs.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Jeff S" <jsolman33@yahoo.com>, "Jörn Engel" <joern@logfs.org>,
linux-mtd@lists.infradead.org, "Josh Boyer" <jwboyer@gmail.com>
Subject: Re: JFFS2 determine writing state
Date: Tue, 15 Jan 2008 20:16:03 +0100 [thread overview]
Message-ID: <20080115191603.GJ22338@lazybastard.org> (raw)
In-Reply-To: <20080115173510.GC16677@shareable.org>
On Tue, 15 January 2008 17:35:10 +0000, Jamie Lokier wrote:
>
> Oh, ok, I thought it at least merged things in the page cache like
> most other filesystems. It seems it's more like O_DSYNC - or more
> like O_SYNC (commits metadata changed for every write too)?
I don't think there is a really good equivalent. Writes happen
immediatly, but the changes may not become effective immediatly. In a
way, the worst of both worlds. :)
> Is there a particular advantage, in terms of flash overhead,
> compression, or mount/gc times, to writing blocks with a particular
> size and alignment, such as 4k size and 4k offset-alignment-in-file?
4k size and 4k alignment is best for all the reasons you cited above.
> Also, does LogFS (which I want to try later) have similar
> characteristics?
At the moment, yes. Most likely I won't get the caching part done
before LCA.
Jörn
--
Victory in war is not repetitious.
-- Sun Tzu
next prev parent reply other threads:[~2008-01-15 19:25 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
2008-01-15 17:35 ` Jamie Lokier
2008-01-15 19:16 ` Jörn Engel [this message]
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=20080115191603.GJ22338@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