[RFC/PATCH 1/1] ubi: Add ubiblock driver

richard -rw- weinberger richard.weinberger at gmail.com
Tue Nov 20 18:59:22 EST 2012

On Tue, Nov 20, 2012 at 11:39 PM, Ezequiel Garcia <elezegarcia at gmail.com> wrote:
> Block device emulation on top of ubi volumes with read/write support.
> Block devices get automatically created for each ubi volume present.
> Each ubiblock is fairly cheap since it's based on workqueues
> and not on threads.
> Read/write access is expected to work fairly well because the
> request queue at block elevator orders block transfers to be space-effective.
> In other words, it's expected that reads and writes gets ordered
> to point to the same LEB.
> To help this and reduce access to the UBI volume, a 1-LEB size
> write-back cache has been implemented.
> Every read and every write, goes through this cache and the write is
> only done when a request arrives to read or write to a different LEB
> or when the device is released, when the last file handle is closed.

Did you also benchmark your driver with two caches?
(One for reading and one for writing.)
By using two caches you can lower the amount of atomic LEB changes.

Maybe it would be also good to ensure that an cache entry becomes not too old.


More information about the linux-mtd mailing list