Re: [libvirt] [PATCH v3 16/28] lock_driver: Introduce KEEP_OPEN flags

2018-09-03 Thread Michal Privoznik
On 08/31/2018 02:32 PM, John Ferlan wrote: > > > On 08/27/2018 04:08 AM, Michal Privoznik wrote: >> This flag causes connection to be opened when needed (e.g. when >> calling virLockManagerLockDaemonAcquire for the first time) and >> instead of closing it at the end of such API store it in >>

Re: [libvirt] [PATCH v3 16/28] lock_driver: Introduce KEEP_OPEN flags

2018-08-31 Thread John Ferlan
On 08/27/2018 04:08 AM, Michal Privoznik wrote: > This flag causes connection to be opened when needed (e.g. when > calling virLockManagerLockDaemonAcquire for the first time) and > instead of closing it at the end of such API store it in > privateData so that it can be reused by later calls. >

[libvirt] [PATCH v3 16/28] lock_driver: Introduce KEEP_OPEN flags

2018-08-27 Thread Michal Privoznik
This flag causes connection to be opened when needed (e.g. when calling virLockManagerLockDaemonAcquire for the first time) and instead of closing it at the end of such API store it in privateData so that it can be reused by later calls. This is needed because if a resource is acquired and