On Mon, May 09, 2016 at 04:43:44PM +0200, Michal Privoznik wrote:
> On 05.05.2016 18:10, Daniel P. Berrange wrote:
> > On Thu, Apr 28, 2016 at 12:04:47PM +0200, Michal Privoznik wrote:
> >>
> >
> > While it looks ok-ish in the context of the RecvAll function,
> > because you have skipFunc +
On 05.05.2016 18:10, Daniel P. Berrange wrote:
> On Thu, Apr 28, 2016 at 12:04:47PM +0200, Michal Privoznik wrote:
>>
>
> While it looks ok-ish in the context of the RecvAll function,
> because you have skipFunc + recvFunc both being invoked
> asynchronously, this design feels a quite odd when
On Thu, Apr 28, 2016 at 12:04:47PM +0200, Michal Privoznik wrote:
> So, after couple of sleepless nights and headaches I'm proud to
> announce that finally got this working.
>
>
> What?
> Our regular streams that are can be used to transfer disk images
> for domains are unaware of any
On 04/28/2016 06:04 AM, Michal Privoznik wrote:
> So, after couple of sleepless nights and headaches I'm proud to
> announce that finally got this working.
>
>
> What?
> Our regular streams that are can be used to transfer disk images
> for domains are unaware of any sparseness. Therefore they
On 28.04.2016 12:04, Michal Privoznik wrote:
> Notes?
> Oh, patches 01-03 have been ACKed already, but are not pushed yet
> because of the freeze. But since this feature build on the top of
> them, I'm sending them too.
Just a notice that I've pushed those patches, so while trying to apply
this
So, after couple of sleepless nights and headaches I'm proud to
announce that finally got this working.
What?
Our regular streams that are can be used to transfer disk images
for domains are unaware of any sparseness. Therefore they have
two limitations:
a) transferring big but sparse image can
