Bug 1282795
Summary: | RFE: streams: vol-upload/download to efficiently transfer sparseness | |||
---|---|---|---|---|
Product: | [Community] Virtualization Tools | Reporter: | Daniel Berrangé <berrange> | |
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | |
Status: | CLOSED DUPLICATE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | unspecified | CC: | crobinso, kchamart, mbooth, rbalakri | |
Target Milestone: | --- | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1282859 (view as bug list) | Environment: | ||
Last Closed: | 2016-04-10 22:44:17 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1282859 |
Description
Daniel Berrangé
2015-11-17 12:54:13 UTC
Don't know if this is the appropriate forum for a libvirt api discussion. There are 2 parts to this. There's the protocol part which you mention above, which will be a huge performance improvement. With just this in place, the flow would be: 1. Client reads hole from relevant metadata. 2. Client generates 4GB of zeroes. 3. Client passes 4GB of zeroes to libvirt. 4. libvirt scans 4GB of zeroes, and determines that they're all zeroes. 5. libvirt sends hole across network. 6. dest libvirt generates 4GB of zeroes. 7. dest scans 4GB of zeroes, and determines that they're all zeroes. 8. dest writes hole to disk. While it would require a new api, or an extension to the existing api, it would be much nicer to be able to do: 1. Client reads hole from relevant metadata. 2. Client sends hole to libvirt. 3. libvirt sends hole to dest. 4. dest writes hole to disk. Since this is being tracked against RHEL, which is actually going to motivate change compared to the upstream tracker, duping to the RHEL bug *** This bug has been marked as a duplicate of bug 1282859 *** |