Re: [libvirt] [PATCH v3 29/31] Introduce virStorageVol{Download, Upload}Flags

2017-05-17 Thread John Ferlan
On 05/17/2017 12:30 PM, Michal Privoznik wrote: > On 05/17/2017 05:42 PM, John Ferlan wrote: >> >> >> On 05/16/2017 10:04 AM, Michal Privoznik wrote: >>> These flags to APIs will tell if caller wants to use sparse >>> stream for storage transfer. At the same time, it's safe to >>> enable them in

Re: [libvirt] [PATCH v3 29/31] Introduce virStorageVol{Download, Upload}Flags

2017-05-17 Thread Michal Privoznik
On 05/17/2017 05:42 PM, John Ferlan wrote: > > > On 05/16/2017 10:04 AM, Michal Privoznik wrote: >> These flags to APIs will tell if caller wants to use sparse >> stream for storage transfer. At the same time, it's safe to >> enable them in storage driver frontend and rely on our backends >> chec

Re: [libvirt] [PATCH v3 29/31] Introduce virStorageVol{Download, Upload}Flags

2017-05-17 Thread John Ferlan
On 05/16/2017 10:04 AM, Michal Privoznik wrote: > These flags to APIs will tell if caller wants to use sparse > stream for storage transfer. At the same time, it's safe to > enable them in storage driver frontend and rely on our backends > checking the flags. This way we can enable specific flags

[libvirt] [PATCH v3 29/31] Introduce virStorageVol{Download, Upload}Flags

2017-05-16 Thread Michal Privoznik
These flags to APIs will tell if caller wants to use sparse stream for storage transfer. At the same time, it's safe to enable them in storage driver frontend and rely on our backends checking the flags. This way we can enable specific flags only on some specific backends, e.g. enable VIR_STORAGE_V