From: "Jörn Engel" <joern@logfs.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>,
penberg@cs.helsinki.fi, ext-adrian.hunter@nokia.com,
jwboyer@gmail.com, "Artem B. Bityutskiy" <dedekind@yandex.ru>
Subject: Re: UBIFS vs Logfs (was [RFC PATCH] UBIFS - new flash file system)
Date: Wed, 9 Apr 2008 23:32:41 +0200 [thread overview]
Message-ID: <20080409213241.GA12179@logfs.org> (raw)
In-Reply-To: <20080409210907.GA9683@ucw.cz>
On Wed, 9 April 2008 23:09:07 +0200, Pavel Machek wrote:
>
> I'd like compressed filesystem for maps and lingvistic data... but
> will the flash flesystems have 'reasonable' performance when used on
> harddrive?
If someone implemented readpages(), that might be possible - depending
on your definition of 'reasonable' and your workload.
Writes will hit the disk roughly in order. When readahead requests a
bunch of pages, there is some chance of them being adjacent and having
the block layer combine most of the bios into a few large ones.
The main drawbacks are:
- No reservations. If data is written in random order or several
writers chew away in parallel, write order will be fairly pessimal.
- No readahead yet. Wouldn't be hard to do.
- Garbage collection completely ignores fragmentation. If segments are
needed and one contains a nice long extend from a single file, that
data will be written elsewhere, often split between two segments.
Rinse, repeat and fragmentation will increase over time.
- File creation/deletion currently will cause disk heads to jump in
triangles. This hurts write performance on most flash media as well,
so it will get changed reasonably soon.
All of those are solvable. Some will definitely be solved because the
help performance on flash media as well. Other may or may not.
Jörn
--
When people work hard for you for a pat on the back, you've got
to give them that pat.
-- Robert Heinlein
next prev parent reply other threads:[~2008-04-09 21:33 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
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 [this message]
-- 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=20080409213241.GA12179@logfs.org \
--to=joern@logfs.org \
--cc=dedekind@yandex.ru \
--cc=ext-adrian.hunter@nokia.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=pavel@ucw.cz \
--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.