public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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: Wed, 4 Jun 2008 08:18:41 +0200	[thread overview]
Message-ID: <20080604061841.GA6492@logfs.org> (raw)
In-Reply-To: <20080603185659.GB6899@shareable.org>

On Tue, 3 June 2008 19:56:59 +0100, Jamie Lokier wrote:
> 
> If that's the logfs journal - why would extra static tree depth near
> the root add any write-commit overhead as you said in the grandparent
> post? :-)

Because I only do it for the root of the tree, as of today.

> (Btw, I thought a difference between logfs and ubifs is the latter
> does async writes?  Or do they both?)

Logfs does async writes for metadata, not for payload data.  That is
enough to get close to jffs2 write performance.  For long streaming
writes it should perform identical to ubifs, short bursts look faster in
ubifs, as the data only goes to cache, not to flash.  Frequent rewrites
of the same data without sync in between are where ubifs currently wins.

Jörn

-- 
It does not require a majority to prevail, but rather an irate,
tireless minority keen to set brush fires in people's minds.
-- Samuel Adams

      reply	other threads:[~2008-06-04  6:18 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
2008-06-03 18:56           ` Jamie Lokier
2008-06-04  6:18             ` Jörn Engel [this message]

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=20080604061841.GA6492@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