From: twebb <taliaferro62@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: ubifs wear leveling across entire device
Date: Thu, 3 Dec 2009 12:31:23 -0500 [thread overview]
Message-ID: <dbdb2ea60912030931j380a7702hc92d4fbe72341730@mail.gmail.com> (raw)
I'm confused about how wear leveling occurs across the entire device
in the following example. Could someone help me understand what I'm
missing?
4 GiB flash device (nand MLC):
4 MTD partitions defined:
0 - "p1" - 0x00000000 - 0x00800000
1 - "p2" - 0x00800000 - 0x10000000
2 - "p3" - 0x10000000 - 0x80000000
3 - "p4" - 0x80000000 - 0x100000000
kernel args specify 3 ubi volumes:
ubi.mtd=p1 ubi.mtd=p2 ubi.mtd=p3
(p4 is reserved and no volumes or filesystems sit on top of it)
The "vol_size" for each of the ubi volumes (as specified in the
ubinize cfg file) is slightly less than the corresponding mtd
partition size. The volumes are specified as dynamic because they
need to be RW.
Thanks,
twebb
next reply other threads:[~2009-12-03 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 17:31 twebb [this message]
2009-12-04 11:31 ` ubifs wear leveling across entire device Adrian Hunter
2009-12-07 15:41 ` twebb
2009-12-07 20:05 ` Adrian Hunter
2009-12-07 22:44 ` twebb
2009-12-08 6:36 ` Artem Bityutskiy
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=dbdb2ea60912030931j380a7702hc92d4fbe72341730@mail.gmail.com \
--to=taliaferro62@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