Re: [libvirt] [PATCH 3/3] Implement non-pool-blocking volume allocation for FS volumes

Implement non-pool-blocking volume allocation for FS volumes. We setup the volume object, then drop the pool lock, and start the actual storage allocation. Certain pool operations will be blocked (start, stop, destroy, refresh), but the basic things like volume listings will still work. This also allows storage allocation progress reporting: the API user can watch the volume object in a separate thread, polling it's 'info' for update to date capacity/allocation reporting.

+ /* Make a shallow copy of the 'defined' volume definition, since the + * original allocation value will change as the user polls 'info', + * but we only need the initial requested values + */ + memcpy(buildvoldef, voldef, sizeof(*voldef)); + voldef = NULL; + + /* Drop the pool lock during volume allocation */ + pool->asyncjobs++; + virStoragePoolObjUnlock(pool); + + buildvoldef->building = 1; + buildret = backend->buildVol(obj->conn, buildvoldef); + buildvoldef->building = 0; + + virStoragePoolObjLock(pool); + pool->asyncjobs--;