> On 27 Feb 2018, at 16.57, Javier González <jg@xxxxxxxxxxx> wrote: > > Currently, the device geometry is stored redundantly in the nvm_id and > nvm_geo structures at a device level. Moreover, when instantiating > targets on a specific number of LUNs, these structures are replicated > and manually modified to fit the instance channel and LUN partitioning. > > Instead, create a generic geometry around nvm_geo, which can be used by > (i) the underlying device to describe the geometry of the whole device, > and (ii) instances to describe their geometry independently. > > Since these share a big part of the geometry, create a nvm_common_geo > structure that keeps the static geoometry values that are shared across > instances. > > As we introduce support for 2.0, these structures allow to abstract > spec. specific values and present a common geometry to targets. > > Signed-off-by: Javier González <javier@xxxxxxxxxxxx> > --- > Please ignore this commit message for now. It’s not updated... Javier
