From: Artem Bityutskiy <dedekind@infradead.org>
To: Jamie Lokier <jamie@shareable.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: big flash disks?
Date: Mon, 02 Jun 2008 08:59:19 +0300 [thread overview]
Message-ID: <1212386359.31023.154.camel@sauron> (raw)
In-Reply-To: <20080601184239.GA11135@shareable.org>
On Sun, 2008-06-01 at 19:42 +0100, Jamie Lokier wrote:
> Some people developing newer flash filesystems (UBIFS, Logfs,
> FAT-over-UBI :-) and interested in flash filesystem performance might
> be interested in this slashdot comment:
>
> http://slashdot.org/comments.pl?sid=569439&cid=23618215
>
> They're implying that UBIFS and Logfs aren't suitable for high
> performance writes and/or large flash, and don't work well with up and
> coming flash disks either.
>
> Also that patents may get in the way.
>
> I've never heard of MFT before.
People should understand that UBIFS is designed for embedded systems. It
is good for low-price devices where you have just bare flash which is
cheap. SSD is a completely different area and irrelevant to UBIFS. The
same applies for LogFS and YAFFS IMO. Talking about using these FS-es on
SSD is just silly (again IMHO).
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-06-02 5:58 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 [this message]
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
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=1212386359.31023.154.camel@sauron \
--to=dedekind@infradead.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 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.