Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: twebb <taliaferro62@gmail.com>
To: Adrian Hunter <adrian.hunter@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: ubifs wear leveling across entire device
Date: Mon, 7 Dec 2009 10:41:08 -0500	[thread overview]
Message-ID: <dbdb2ea60912070741l7a0dde1dt49ba0f5413accf61@mail.gmail.com> (raw)
In-Reply-To: <4B18F300.7080006@nokia.com>

>>
>> 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)
>
> That is 3 UBI devices not 3 UBI volumes
>

Excuse me.  I'm new to using UBI and UBIFS and am not completely
familiar with the terminology.  I think what I described in the
example is 3 UBI devices, with a single volume associated with each
device.  I had neglected to show that each UBI device had a single
volume.

Maybe there's a better way to word my question.  Does UBI wear
leveling occur independently across each MTD device (p1, p2, and p3
only in example above) or does it somehow occur over the entire
physical device (p1-p4 inclusive)?

I'm trying to understand this so I can determine how to partition the
physical device to provide the best wear leveling, while still
allowing a portion of the physical device (p4) to exist outside of any
UBI device or volume.

Thanks,
twebb

  reply	other threads:[~2009-12-07 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 17:31 ubifs wear leveling across entire device twebb
2009-12-04 11:31 ` Adrian Hunter
2009-12-07 15:41   ` twebb [this message]
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=dbdb2ea60912070741l7a0dde1dt49ba0f5413accf61@mail.gmail.com \
    --to=taliaferro62@gmail.com \
    --cc=adrian.hunter@nokia.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