1. 14 11月, 2013 1 次提交
  2. 01 2月, 2013 1 次提交
  3. 26 1月, 2013 2 次提交
    • P
      mirror: add buf-size argument to drive-mirror · 08e4ed6c
      Paolo Bonzini 提交于
      This makes sense when the next commit starts using the extra buffer space
      to perform many I/O operations asynchronously.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      08e4ed6c
    • P
      mirror: perform COW if the cluster size is bigger than the granularity · b812f671
      Paolo Bonzini 提交于
      When mirroring runs, the backing files for the target may not yet be
      ready.  However, this means that a copy-on-write operation on the target
      would fill the missing sectors with zeros.  Copy-on-write only happens
      if the granularity of the dirty bitmap is smaller than the cluster size
      (and only for clusters that are allocated in the source after the job
      has started copying).  So far, the granularity was fixed to 1MB; to avoid
      the problem we detected the situation and required the backing files to
      be available in that case only.
      
      However, we want to lower the granularity for efficiency, so we need
      a better solution.  The solution is to always copy a whole cluster the
      first time it is touched.  The code keeps a bitmap of clusters that
      have already been allocated by the mirroring job, and only does "manual"
      copy-on-write if the chunk being copied is zero in the bitmap.
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      b812f671
  4. 24 10月, 2012 2 次提交
  5. 29 9月, 2012 2 次提交
  6. 29 8月, 2012 1 次提交
  7. 10 5月, 2012 1 次提交
  8. 27 4月, 2012 1 次提交
  9. 29 2月, 2012 1 次提交