From: Jamie Lokier <jamie@shareable.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-mtd@lists.infradead.org, Alex Dubov <oakad@yahoo.com>
Subject: Re: Support of removable MTD devices and other advanced features (follow-up from lkml)
Date: Sun, 25 May 2008 17:35:56 +0100 [thread overview]
Message-ID: <20080525163555.GA7112@shareable.org> (raw)
In-Reply-To: <20080525162426.GA14741@logfs.org>
Jörn Engel wrote:
> > That seems like it would cause uneven wear-levelling in some
> > situations. Specifically, each time you need to erase a block which
> > has not been completely written, because you need to write a
> > contiguous record larger than the remaining space.
> >
> > I don't know it was a physical requirement of some chips, thanks for
> > clarifying.
>
> The "progressive" limitation only concerns writes _within_ eraseblocks.
> It has no impact on wear leveling.
I understood that.
I mean that progressive writing may cause more wear towards the
beginning of _each_ eraseblock, because you'll write more often at the
start of each eraseblock than the end. That's if wear is at all a
function of writes, and not solely erase operations.
There's another curious thought: do individual flash bit cells wear
out more quickly when written to "0" or left at "1"? I doubt it, but
if it did make a difference, it would make a case for xoring data with
predictable pseudo-random bits.
-- Jamie
next prev parent reply other threads:[~2008-05-25 16:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 13:59 Support of removable MTD devices and other advanced features (follow-up from lkml) Alex Dubov
2008-05-21 6:47 ` Artem Bityutskiy
2008-05-21 8:41 ` Jörn Engel
2008-05-22 1:30 ` Alex Dubov
2008-05-22 15:10 ` Jörn Engel
2008-05-23 2:47 ` Alex Dubov
2008-05-23 5:50 ` Jörn Engel
2008-05-23 9:33 ` Alex Dubov
2008-05-23 9:59 ` Jörn Engel
2008-05-23 12:49 ` Alex Dubov
2008-05-23 13:28 ` Jörn Engel
2008-05-24 13:12 ` Alex Dubov
2008-05-24 17:56 ` Jörn Engel
2008-05-25 3:41 ` Alex Dubov
2008-05-25 7:25 ` Jörn Engel
2008-05-25 13:30 ` Jamie Lokier
2008-05-25 16:24 ` Jörn Engel
2008-05-25 16:35 ` Jamie Lokier [this message]
2008-05-25 16:55 ` Jörn Engel
2008-05-26 2:12 ` Alex Dubov
2008-05-21 9:06 ` David Woodhouse
2008-05-21 9:29 ` Jörn Engel
2008-05-21 15:20 ` Alex Dubov
2008-05-21 15:22 ` David Woodhouse
2008-05-21 15:41 ` Alex Dubov
2008-05-21 20:45 ` Jörn Engel
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=20080525163555.GA7112@shareable.org \
--to=jamie@shareable.org \
--cc=joern@logfs.org \
--cc=linux-mtd@lists.infradead.org \
--cc=oakad@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.