Unmapped I/O

Fri Dec 21 11:53:22 UTC 2012

On 20 December 2012 21:15, Konstantin Belousov <kostikbel at gmail.com> wrote:

> Nothing is changed for existing GEOM classes, and it does not mean anything
> for GEOM developers, unless she wants to change the GEOM class to handle
> unmapped BIOs.

Understood, but the intention of my question was: do you recommend
GEOM classes should take the effort and implement unmapped BIOs
whenever possible?

Your change in g_part.c is trivial - this is because g_part doesn't
actually touch the BIO data, only pass it on?