public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Duke <ezbonites@gmail.com>
Cc: linux-mtd@lists.infradead.org, "Jörn Engel" <joern@logfs.org>,
	"Josh Boyer" <jwboyer@gmail.com>,
	"Jamie Lokier" <jamie@shareable.org>,
	"David Woodhouse" <dwmw2@infradead.org>
Subject: Re: jffs2: too few erase blocks
Date: Tue, 30 Oct 2007 21:19:45 +0100	[thread overview]
Message-ID: <20071030201945.GA16322@lazybastard.org> (raw)
In-Reply-To: <79ac09b60710301308m294ae82m79e6ee982208ca35@mail.gmail.com>

On Tue, 30 October 2007 15:08:11 -0500, Duke wrote:
> 
> After all is said and done, can the minimum number of jffs2 blocks be
> determined? Or it varies from system to system? Or flash system type
> (NOR flash in my case).

It can.  Please read jffs2_calc_trigger_levels() in fs/jffs2/build.c.
Maybe those numbers can even be lowered a little.  But you get to do the
math, if that is your wish.

Jörn

-- 
Joern's library part 15:
http://www.knosof.co.uk/cbook/accu06a.pdf

  reply	other threads:[~2007-10-30 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 14:06 jffs2: too few erase blocks Duke
2007-10-25 14:22 ` Josh Boyer
2007-10-25 22:15   ` Jamie Lokier
2007-10-26 17:00     ` Duke
2007-10-26 21:02       ` Duke
2007-10-28 18:02         ` Jamie Lokier
2007-10-29  2:59           ` David Woodhouse
2007-10-29 14:38             ` Jörn Engel
2007-10-29 20:51               ` Jamie Lokier
2007-10-29 21:40                 ` David Woodhouse
2007-10-29 22:50                   ` Jamie Lokier
2007-10-29 21:54                 ` Jörn Engel
2007-10-29 22:46                   ` Jamie Lokier
2007-10-30 16:09                     ` Jörn Engel
2007-10-30 20:08                       ` Duke
2007-10-30 20:19                         ` Jörn Engel [this message]
2007-10-30 21:42                           ` Duke

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=20071030201945.GA16322@lazybastard.org \
    --to=joern@logfs.org \
    --cc=dwmw2@infradead.org \
    --cc=ezbonites@gmail.com \
    --cc=jamie@shareable.org \
    --cc=jwboyer@gmail.com \
    --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