public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Should flash hardware look like UBI?
Date: Tue, 06 Oct 2009 14:07:52 +0100	[thread overview]
Message-ID: <1254834472.14541.1331.camel@macbook.infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0910061442530.2638@localhost.localdomain>

On Tue, 2009-10-06 at 14:56 +0200, Thomas Gleixner wrote:
> 
> I guess the bad block hiding might work, but I'm concerned about the
> wear levelling aspect. That's what they usually fail to do in a
> sensible way. When the resulting carefully hidden and obscured
> algorithm is just contrary to what the filesystem expects you are
> again digging holes in your device within no time.

Yeah. It makes a lot of sense for the wear levelling to be done
explicitly by the OS, not in the device.

So maybe we don't want the interface to be _quite_ like UBI.

But if we can let the device handle _some_ of the aspects of the
logical<->physical translation, that would be interesting. Partly
because it could do the full scan of the device at startup _internally_,
and it wouldn't slow down the OS.

I'd be happy with limiting it to _just_ what hard drives to; ECC and a
1:1 remapping of blocks. Basically 'hardware acceleration for UBI'.

-- 
dwmw2

  reply	other threads:[~2009-10-06 13:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-05 14:05 Should flash hardware look like UBI? David Woodhouse
2009-10-06 11:21 ` Thomas Gleixner
2009-10-06 12:05   ` David Woodhouse
2009-10-06 12:56     ` Thomas Gleixner
2009-10-06 13:07       ` David Woodhouse [this message]
2009-10-06 14:40 ` Bill Gatliff

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=1254834472.14541.1331.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.de \
    /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