public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Russ Dill <russ.dill@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: squashfs and NAND flash
Date: Fri, 28 Apr 2006 13:12:25 +0100	[thread overview]
Message-ID: <445206A9.7040803@lougher.demon.co.uk> (raw)
In-Reply-To: <625fc13d0604271806q422fb20cm2f748cd669d5080@mail.gmail.com>

Josh Boyer wrote:
> On 4/27/06, Phillip Lougher <phillip@lougher.demon.co.uk> wrote:
> 
>> A couple of years ago I did some work making Squashfs work with NAND.
>> Because of the inherent unreliability of NAND, and the constant MTD code
>> base changes, I decided not to make this work publically available.
> 
> 
> Just out of curiosity, did you do this in the filesystem itself or via
> a FTL like what has been discussed so far?

It was done in the filesystem itself, in a way similar to that which has 
been discussed.  Bad blocks were skipped, and on good blocks the block 
number of the stored block was written to the OOB data area.  Blocks 
were accessed by going to the expected block, and (if this wasn't the 
expected block due to bad block skipping) then scanning forwards until 
the expected block was found.

> 
>> Providing native NAND support in Squashfs represents too much work for
>> absolutely no gain.  It is unlikely this is going to change in the near
>> future.
> 
> 
> There is gain in providing a generic mechansim that block type
> filesystems can use to do this though.  Simple economics are going to
> drive more devices to have NAND parts than NOR, so something needs to
> eventually fill this gap.
> 

I think I was maybe a little unclear as to what I meant.  I think a 
generic mechanism that block filesystems could use would be very useful. 
  What I meant was providing NAND support in Squashfs would generate a 
lot more support requests and require more maintenance.  Unfortunately, 
I don't have the resources to do this.

Phillip

  reply	other threads:[~2006-04-28 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-25 10:02 squashfs and NAND flash Anil Gupta
2006-04-25 10:26 ` Andy Hawkins
2006-04-27 21:33   ` Russ Dill
2006-04-27 23:35     ` Phillip Lougher
2006-04-28  1:06       ` Josh Boyer
2006-04-28 12:12         ` Phillip Lougher [this message]
2006-04-28 12:36           ` Josh Boyer
2006-04-25 12:21 ` Vitaly Wool

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=445206A9.7040803@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=jwboyer@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=russ.dill@gmail.com \
    /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