From: "H. Peter Anvin" <hpa@zytor.com>
To: Artem Bityutskiy <dedekind@yandex.ru>
Cc: "Andi Kleen" <andi@firstfloor.org>,
"Tomasz Chmielewski" <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
penberg@cs.helsinki.fi, "Jörn Engel" <joern@logfs.org>,
ext-adrian.hunter@nokia.com, jwboyer@gmail.com
Subject: Re: UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system)
Date: Tue, 01 Apr 2008 09:27:36 -0700 [thread overview]
Message-ID: <47F26278.5070009@zytor.com> (raw)
In-Reply-To: <47F21B47.4000206@yandex.ru>
Artem Bityutskiy wrote:
> Andi Kleen wrote:
>> Artem Bityutskiy <dedekind@yandex.ru> writes:
>>
>>> Tomasz Chmielewski wrote:
>>>> For me, the motivators to wait for LogFS are mainly the facts that it
>>>> can work on traditional block devices, and not only on pure flash:
>>> Sorry Thomasz, for me this makes zero sense. There are _much_ better
>>> file
>>> systems for block devices.
>>
>> I think he refers to flash disks appearing as block devices, like
>> usb sticks or similar.
>
> Right, I also meant that in my opinion it makes more sense to use
> traditional
> file-systems like ext3 on USB-key/MMC and the like stuff (which I
> confusingly
> referred as "block devices"), or may be something more "heavy-weight" like
> XFS or JFS (never tried them, though).
>
Well, even auto-levelling storage should benefit from a filesystem which
minimizes the total number of flash sectors churned, which means doing
as few writes as possible and to large, contiguous sections.
-hpa
next prev parent reply other threads:[~2008-04-01 16:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 8:02 UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system) Tomasz Chmielewski
2008-04-01 8:45 ` Artem Bityutskiy
2008-04-01 9:03 ` Jörn Engel
2008-04-01 9:09 ` Artem Bityutskiy
2008-04-01 9:31 ` Jörn Engel
2008-04-01 9:39 ` Tomasz Chmielewski
2008-04-01 9:57 ` Artem Bityutskiy
2008-04-02 14:17 ` Tomasz Chmielewski
2008-04-02 14:22 ` Jörn Engel
2008-04-01 11:06 ` Andi Kleen
2008-04-01 11:23 ` Artem Bityutskiy
2008-04-01 16:27 ` H. Peter Anvin [this message]
2008-04-01 21:26 ` Willy Tarreau
2008-04-02 4:47 ` Artem Bityutskiy
2008-04-02 6:25 ` Willy Tarreau
2008-04-02 7:17 ` Artem Bityutskiy
2008-04-09 21:09 ` Pavel Machek
2008-04-09 21:32 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2008-03-27 14:55 [RFC PATCH] UBIFS - new flash file system Artem Bityutskiy
2008-03-31 12:29 ` Jan Engelhardt
2008-03-31 12:47 ` Adrian Hunter
2008-03-31 13:20 ` Jörn Engel
2008-04-01 5:26 ` UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system) Artem Bityutskiy
2008-04-01 5:28 ` Artem Bityutskiy
2008-04-01 5:56 ` Artem Bityutskiy
2008-04-01 9:25 ` Jörn Engel
2008-04-01 9:39 ` Artem Bityutskiy
2008-04-01 10:51 ` Jörn Engel
2008-04-01 11:17 ` Artem Bityutskiy
2008-04-01 9:19 ` Jörn Engel
2008-04-01 9:46 ` Artem Bityutskiy
2008-04-01 11:16 ` 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=47F26278.5070009@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=dedekind@yandex.ru \
--cc=ext-adrian.hunter@nokia.com \
--cc=joern@logfs.org \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=penberg@cs.helsinki.fi \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.