public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Bernhard Priewasser <bernhard@prie.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Compiling JFFS3
Date: Wed, 10 Aug 2005 12:05:57 +0200	[thread overview]
Message-ID: <20050810100557.GA18149@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <42F9C980.7030301@prie.de>

On Wed, 10 August 2005 11:31:44 +0200, Bernhard Priewasser wrote:
>
> To: linux-mtd@lists.infradead.org

Please always reply to all.  I hate to miss interesting stuff, just
because some idiot removed me from the Cc: list.

[ For political correctness' sake.  I didn't call you an idiot yet.
Only if you _continue_ to misbehave in this way, I _will_ call you
that.  So please... ;) ]

> 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 :)

The name "JFFS3" ist confusing.  For that very reason, I consider it
rightout harmful to call anything "JFFS3".  Artem has a different
opinion.  It's a free world, everyone has the right to be wrong, if he
so desires. ;)

JFFS has a strictly log-structured design.  JFFS2 is still
log-structured, although not strictly anymore.  You could call it a
chaptered log - strictly log-structured within a chapter, completely
independent chapters.  JFFS3 (the old one, which Artem just removed)
was still supposed to be log-structured.  So the name made sense.  It
was similar in design.

The next flash FS, whatever it will look like, will not be log
structure anymore.  At least, noone I know of is trying to follow that
road anymore.  Log-structuring simply doesn't scale.  Therefore, this
fundamental change in design should not be hidden behind a name like
"JFFS3" - especially since it could also describe the last, failed
approach.

Jörn

-- 
Schrödinger's cat is <BLINK>not</BLINK> dead.
-- Illiad

  parent reply	other threads:[~2005-08-10 10:05 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
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 [this message]
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=20050810100557.GA18149@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox