Re: [libvirt] [PATCH] storage: Don't hold storage pool locked during wipeVol

2018-08-17 Thread John Ferlan
On 08/17/2018 05:40 AM, Michal Privoznik wrote: > On 08/16/2018 05:22 PM, John Ferlan wrote: >> >> >> On 08/13/2018 06:49 AM, Michal Privoznik wrote: >>> Currently the way virStorageVolWipe() works is it looks up >>> pool containing given volume and hold it locked throughout while >>> API

Re: [libvirt] [PATCH] storage: Don't hold storage pool locked during wipeVol

2018-08-17 Thread Michal Privoznik
On 08/16/2018 05:22 PM, John Ferlan wrote: > > > On 08/13/2018 06:49 AM, Michal Privoznik wrote: >> Currently the way virStorageVolWipe() works is it looks up >> pool containing given volume and hold it locked throughout while >> API execution. This is suboptimal because wiping a volume means >>

Re: [libvirt] [PATCH] storage: Don't hold storage pool locked during wipeVol

2018-08-16 Thread John Ferlan
On 08/13/2018 06:49 AM, Michal Privoznik wrote: > Currently the way virStorageVolWipe() works is it looks up > pool containing given volume and hold it locked throughout while > API execution. This is suboptimal because wiping a volume means > writing data to it which can take ages. And if the

[libvirt] [PATCH] storage: Don't hold storage pool locked during wipeVol

2018-08-13 Thread Michal Privoznik
Currently the way virStorageVolWipe() works is it looks up pool containing given volume and hold it locked throughout while API execution. This is suboptimal because wiping a volume means writing data to it which can take ages. And if the whole pool is locked during that operation no other API can