linux-kernel - Re: Filesystem for block devices using flash storage?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Oct 2008 20:13:33 +0200
From:	Jörn Engel <joern@...fs.org>
To:	Chris Snook <csnook@...hat.com>
Cc:	Stefan Monnier <monnier@....umontreal.ca>,
	linux-kernel@...r.kernel.org
Subject: Re: Filesystem for block devices using flash storage?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/