From: "Jörn Engel" <joern@logfs.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: big flash disks?
Date: Tue, 3 Jun 2008 20:12:26 +0200 [thread overview]
Message-ID: <20080603181226.GF1224@logfs.org> (raw)
In-Reply-To: <20080602124822.GB2679@shareable.org>
On Mon, 2 June 2008 13:48:22 +0100, Jamie Lokier wrote:
>
> The basic idea is for a pointer in a tree node to point not to one
> child, but to a small set of potential children. The child-set are a
> journal in the jffs2 sense. When reading, you read each block of the
> child-set, and pick the most recent. This slows down reading, but
> reduces the amount of writing. You still read in O(log tree_size)
> blocks, and since most of the extra reads are hot-cache internal tree
> blocks, the amount of extra reading is quite small. Child-sets can
> overlap to reduce storage duplication, at cost of more operations -
> it's a heuristic balancing act. Child-sets are not used for all tree
> nodes, especially data. They can be invoked and destroyed dynamically
> using heuristics to detect some parts of the tree undergoing lots of
> write+sync sequences and others being coalescable writes or not
> written.
This is actually a good explanation of the logfs journal. :)
Jörn
--
All art is but imitation of nature.
-- Lucius Annaeus Seneca
next prev parent reply other threads:[~2008-06-03 18:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 18:42 big flash disks? Jamie Lokier
2008-06-01 20:41 ` Josh Boyer
2008-06-02 5:59 ` Artem Bityutskiy
2008-06-02 8:23 ` Jörn Engel
2008-06-02 10:43 ` Jamie Lokier
2008-06-02 11:55 ` Jörn Engel
2008-06-02 12:32 ` Jamie Lokier
2008-06-03 18:09 ` Jörn Engel
2008-06-03 18:44 ` Jamie Lokier
2008-06-04 6:25 ` Jörn Engel
2008-06-02 7:28 ` Jörn Engel
2008-06-02 10:41 ` Jamie Lokier
2008-06-02 11:43 ` Jörn Engel
2008-06-02 12:48 ` Jamie Lokier
2008-06-03 18:12 ` Jörn Engel [this message]
2008-06-03 18:56 ` Jamie Lokier
2008-06-04 6:18 ` 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=20080603181226.GF1224@logfs.org \
--to=joern@logfs.org \
--cc=jamie@shareable.org \
--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