From: Bernhard Priewasser <bernhard@prie.de>
To: linux-mtd@lists.infradead.org
Subject: Re: Compiling JFFS3
Date: Wed, 10 Aug 2005 11:31:44 +0200 [thread overview]
Message-ID: <42F9C980.7030301@prie.de> (raw)
In-Reply-To: <42F9C612.2050301@yandex.ru>
Artem B. Bityuckiy wrote:
> Bernhard Priewasser wrote:
>> Ferenc Havasi's improvements are doing well? Confusing...
> His improvements are going to go into JFFS2 AFAIK
Ah, OK. To sum up (for my understanding): Ferenc's improvements (mount
time, compression) were - beside others - part of JFFS3. JFFS3 design in
its current form is not satisfactory, it will be cancelled. Anyway,
Ferenc's improvements are good and should/will be merged into JFFS2.
In parallel, there are some ideas for solving JFFS2 problems like
described in the (very nice) "JFFS3 design issues" (scaling: mount time,
memory consumption, access time). This will be the "new" JFFS3, current
solutions for scaling and stuff are not available or not satisfactory.
Correct until now? Still a bit confusing :)
Bernhard
next prev parent reply other threads:[~2005-08-10 9:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-10 8:26 Compiling JFFS3 Bernhard Priewasser
2005-08-10 8:38 ` Jörn Engel
2005-08-10 8:48 ` Bernhard Priewasser
2005-08-10 9:02 ` Artem B. Bityuckiy
2005-08-10 9:11 ` Bernhard Priewasser
2005-08-10 9:17 ` Artem B. Bityuckiy
2005-08-10 9:31 ` Bernhard Priewasser [this message]
2005-08-10 9:45 ` Artem B. Bityuckiy
2005-08-10 9:54 ` Bernhard Priewasser
2005-08-10 10:00 ` Artem B. Bityuckiy
2005-08-10 10:05 ` Jörn Engel
2005-08-10 10:14 ` Steven Scholz
2005-08-10 10:28 ` Bernhard Priewasser
2005-08-10 10:28 ` Jörn Engel
2005-08-10 10:30 ` Steven Scholz
2005-08-10 10:34 ` Artem B. Bityuckiy
2005-08-10 10:37 ` Steven Scholz
2005-08-10 10:42 ` Artem B. Bityuckiy
2005-08-10 10:48 ` Jörn Engel
2005-08-12 20:27 ` Jared Hulbert
2005-08-12 21:26 ` Josh Boyer
2005-08-15 9:11 ` Jörn Engel
2005-08-10 10:36 ` Bernhard Priewasser
2005-08-10 10:45 ` Jörn Engel
2005-08-10 8:56 ` Artem B. Bityuckiy
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=42F9C980.7030301@prie.de \
--to=bernhard@prie.de \
--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.