public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Chris Snook <csnook@redhat.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, linux-kernel@vger.kernel.org
Subject: Re: Filesystem for block devices using flash storage?
Date: Mon, 13 Oct 2008 20:13:33 +0200	[thread overview]
Message-ID: <20081013181333.GB22447@logfs.org> (raw)
In-Reply-To: <48F385B5.1040503@redhat.com>

On Mon, 13 October 2008 13:30:29 -0400, Chris Snook wrote:
> >
> >>logfs tries to solve the write amplification problem by forcing all write 
> >>activity to be sequential.  I'm not sure how mature it is.
> >
> >Still under development.  What exactly do you mean by the write
> >amplification problem?
> 
> Write amplification is where a 512 byte write turns into a 128k write, 
> due to erase block size.

Ah, yes.  Current logfs still triggers that a bit too often.  I'm
currently working on the format changes to avoid the amplification as
much as possible.

Another nasty side effect of this is that heuristics for wear leveling
are always imprecise.  And wear leveling is still required for most
devices.  See http://www.linuxconf.eu/2007/papers/Engel.pdf

> Intel is claiming a write amplification factor of 1.1.  Either they're 
> using very small erase blocks, or doing something very smart in the 
> controller.

With very small erase blocks the facter should be either 1 or 2, not
1.1.  Most likely they work very much like logfs does, essentially doing
the whole log-structured thing internally.

Jörn

-- 
Das Aufregende am Schreiben ist es, eine Ordnung zu schaffen, wo
vorher keine existiert hat.
-- Doris Lessing

  reply	other threads:[~2008-10-13 18:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 16:38 Filesystem for block devices using flash storage? Stefan Monnier
2008-10-08 20:51 ` Chris Snook
2008-10-11 14:35   ` Pavel Machek
2008-10-11 16:29     ` Arjan van de Ven
2008-10-11 17:51     ` Alan Cox
2008-10-12 13:01     ` Jörn Engel
2008-10-13 10:57       ` Pavel Machek
2008-10-13 12:10         ` Jörn Engel
2008-10-14 18:04     ` Lennart Sorensen
2008-10-12 14:35   ` Jörn Engel
2008-10-13 17:30     ` Chris Snook
2008-10-13 18:13       ` Jörn Engel [this message]
2008-10-13 18:38         ` Chris Snook
2008-10-14 11:18 ` Jörn Engel
2008-10-14 13:05   ` Stefan Monnier

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=20081013181333.GB22447@logfs.org \
    --to=joern@logfs.org \
    --cc=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=monnier@iro.umontreal.ca \
    /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