linux-kernel - Re: [RFC PATCH] UBIFS

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, 31 Mar 2008 15:47:05 +0300
From:	Adrian Hunter <ext-adrian.hunter@...ia.com>
To:	ext Jan Engelhardt <jengelh@...putergmbh.de>
CC:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	LKML <linux-kernel@...r.kernel.org>, joern@...ybastard.org
Subject: Re: [RFC PATCH] UBIFS - new flash file system

Jan Engelhardt wrote:
> 
> On Thursday 2008-03-27 15:55, Artem Bityutskiy wrote:
>>
>> here is a new flash file system developed by Nokia engineers with
>> help of the University of Szeged. The new file-system is called
>> UBIFS, which stands for UBI file system. UBI is the wear-leveling/
>> bad-block handling/volume management layer which is already in
>> mainline (see drivers/mtd/ubi).
>> [...]
> 
> And how does it compare to logfs?

We don't know a lot about logfs, so you will really have to make
your own comparison.  However our general impressions are as follows:

1. In our testing logfs file operations seem to be much slower,
see http://osl.sed.hu/wiki/ubifs/index.php/IOzone

2. logfs code base is much smaller i.e.  UBIFS has 3-4 times as many
lines of code.

3. logfs does not seem to have bad-block handling.

4. logfs does not seem to have wear-leveling.

5. We are not certain how scalable logfs is.

We could be wrong about those things - don't flame us if we are.
Ask us about UBIFS, not logfs.
--
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/