[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120805112337.2a315c75@pixies.home.jungo.com>
Date: Sun, 5 Aug 2012 11:23:37 +0300
From: Shmulik Ladkani <shmulik.ladkani@...il.com>
To: Richard Weinberger <richard@....at>
Cc: artem.bityutskiy@...ux.intel.com, Tim Bird <tim.bird@...sony.com>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"adrian.hunter@...el.com" <adrian.hunter@...el.com>,
"Heinz.Egger@...utronix.de" <Heinz.Egger@...utronix.de>,
"thomas.wucher@...utronix.de" <thomas.wucher@...utronix.de>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"Marius.Mazarel@...l.ro" <Marius.Mazarel@...l.ro>,
"nyoushchenko@...sta.com" <nyoushchenko@...sta.com>
Subject: Re: UBI fastmap updates
Hi,
On Thu, 2 Aug 2012 19:45:38 +0200 Richard Weinberger <richard@....at> wrote:
> Okay, then let's explicitly reserve a few PEBs for fastmap.
> This should be very easy task.
Need to consider what's expected when migrating from a former non-FM
UBI system to an FM enabled system, in the case where all PEBs where
consumed (reserved) in the former system.
> How much PEB should be reserved? 2 x sizeof(fastmap)?
Since FM does not use EBA's atomic LEB change when writing the new
fastmap, but instead implements its own FM "leb change" internally -
then reserving 2x is needed if we'd like to avoid reusing the same
fastmap PEB.
Regards,
Shmulik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists