Re: [libvirt] [PATCH v3 17/28] lock_manager: Introduce virLockManagerCloseConn

2018-09-03 Thread Michal Privoznik
On 08/31/2018 03:26 PM, John Ferlan wrote: > > > On 08/27/2018 04:08 AM, Michal Privoznik wrote: >> After the previous commit we have VIR_LOCK_MANAGER_ACQUIRE_KEEP_OPEN >> flag. This is not enough because it will keep connection open for only >> one instance of drvAcquire + drvRelease call. And w

Re: [libvirt] [PATCH v3 17/28] lock_manager: Introduce virLockManagerCloseConn

2018-08-31 Thread John Ferlan
On 08/27/2018 04:08 AM, Michal Privoznik wrote: > After the previous commit we have VIR_LOCK_MANAGER_ACQUIRE_KEEP_OPEN > flag. This is not enough because it will keep connection open for only > one instance of drvAcquire + drvRelease call. And when starting up a > domain there will be a lot of s

[libvirt] [PATCH v3 17/28] lock_manager: Introduce virLockManagerCloseConn

2018-08-27 Thread Michal Privoznik
After the previous commit we have VIR_LOCK_MANAGER_ACQUIRE_KEEP_OPEN flag. This is not enough because it will keep connection open for only one instance of drvAcquire + drvRelease call. And when starting up a domain there will be a lot of such calls as there will be a lot of paths to relabel and th