public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Larry Doolittle <ldoolitt@recycle.lbl.gov>
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS2_RESERVED_BLOCKS_*
Date: Tue, 02 Oct 2001 17:35:44 +0100	[thread overview]
Message-ID: <30731.1002040544@redhat.com> (raw)
In-Reply-To: <20011002091421.A15650@recycle.lbl.gov>

ldoolitt@recycle.lbl.gov said:
>  Maybe my use is atypical, and maybe 5 blocks is a theoretical
> minimum.  I don't want to sound like a complainer, either -- this file
> system certainly looks like it meets my needs. I guess I just want to
> point out the superficial imbalance between the amount of sweat people
> pour out on projects like busybox to reduce code size by a few kB,
> when there is 320 kB "just lying around" on any JFFS2 on a 64 kB erase
> block chip.

Theoretical minimum is one block, not five. Give me formal proof that 
this is also the _practical_ minimum, and we can drop the 
overly-conservative limits.

Actually, we'd drop it to two, to allow for at least one block going bad on 
us. More than two on NAND flash.

--
dwmw2

  reply	other threads:[~2001-10-02 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02 16:14 JFFS2_RESERVED_BLOCKS_* Larry Doolittle
2001-10-02 16:35 ` David Woodhouse [this message]
2001-10-02 19:45   ` JFFS2_RESERVED_BLOCKS_* dennis noermann
2001-10-02 19:56     ` JFFS2_RESERVED_BLOCKS_* David Woodhouse
2001-10-03 16:29   ` JFFS2_RESERVED_BLOCKS_* Jörn Engel
2001-10-03 22:44     ` JFFS2_RESERVED_BLOCKS_* dennis noermann
2001-10-04  9:34     ` JFFS2_RESERVED_BLOCKS_* David Woodhouse

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=30731.1002040544@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ldoolitt@recycle.lbl.gov \
    --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