Lines Matching full:eraseblocks

57  * initialization UBI finds out that there are available physical eraseblocks
59  * (the physical eraseblocks reserved for bad eraseblocks handling and other
60  * reserved physical eraseblocks are not taken). So, if there is a volume with
62  * eraseblocks will be zero after UBI is loaded, because all of them will be
68  * eraseblocks, depending of particular chip instance. Manufacturers of NAND
69  * chips usually guarantee that the amount of initial bad eraseblocks does not
72  * of good physical eraseblocks the NAND chip on the device will have, but this
78  * Note, first UBI reserves some amount of physical eraseblocks for bad
80  * means that the pool of reserved physical eraseblocks will always be present.
94  *                       physical eraseblocks, don't allow the wear-leveling
137  * eraseblocks.
141  * same on all eraseblocks. UBI will ensure that all new erase counter headers
173  * @used_ebs: total number of used logical eraseblocks in this volume
188  * logical eraseblocks.
195  * 1. Because UBI may erase physical eraseblocks asynchronously, the following
199  * physical eraseblocks P and P1 corresponding to the same logical eraseblock
203  * 2. From time to time UBI moves logical eraseblocks to other physical
204  * eraseblocks for wear-leveling reasons. If, for example, UBI moves L from P
206  * are two physical eraseblocks P and P1 corresponding to L and UBI has to
260  * eraseblocks the data of the volume takes. For dynamic volumes this field is
265  * eraseblocks of this volume. This is very handy when one uses block-oriented
319  * @reserved_pebs: how many physical eraseblocks are reserved for this volume
351  * the physical eraseblocks is used.