Il 15/11/2012 13:21, Wenchao Xia ha scritto:
>
>>>Personally agree, but I want to add a simple wrapper to let libqblock
>>> get user faster. In this way I guess best choice now is making rpc
>>> client and server not mirrored in implemention, server provides
>>> r/w/info retrieving capabilitie
> Il 15/11/2012 05:18, Wenchao Xia ha scritto:
Personally agree, but I want to add a simple wrapper to let libqblock
get user faster. In this way I guess best choice now is making rpc
client and server not mirrored in implemention, server provides
r/w/info retrieving capabilities via XDR proto
Il 15/11/2012 05:18, Wenchao Xia ha scritto:
> Personally agree, but I want to add a simple wrapper to let libqblock
> get user faster. In this way I guess best choice now is making rpc
> client and server not mirrored in implemention, server provides
> r/w/info retrieving capabilities via XDR pr
δΊ 2012-11-14 18:32, Paolo Bonzini ει:
Il 14/11/2012 10:55, Wenchao Xia ha scritto:
In order to resolve OOM issue, I am trying wrap all APIs using
sunrpc, need some suggestion before coding.
Is the client/server approach really necessary or can you write a
library that invokes qemu-nbd/qemu
Il 14/11/2012 10:55, Wenchao Xia ha scritto:
>>In order to resolve OOM issue, I am trying wrap all APIs using
>> sunrpc, need some suggestion before coding.
>
> Is the client/server approach really necessary or can you write a
> library that invokes qemu-nbd/qemu-img?
>
> If there is a startu
> Il 14/11/2012 04:50, Wenchao Xia ha scritto:
>>There are some different way to implement, not sure which would be
>> better:
>>1 keep client as thin as possible, client stores opaque pointer used
>> in server side, for eg, QBlockContext *ctx, client only get a pointer
>> pointing to the a
> On Wed, Nov 14, 2012 at 11:50:06AM +0800, Wenchao Xia wrote:
In order to resolve OOM issue, I am trying wrap all APIs using
sunrpc, need some suggestion before coding.
Is the client/server approach really necessary or can you write a
library that invokes qemu-nbd/qemu-img?
If there is a s
Il 14/11/2012 04:50, Wenchao Xia ha scritto:
> There are some different way to implement, not sure which would be
> better:
> 1 keep client as thin as possible, client stores opaque pointer used
> in server side, for eg, QBlockContext *ctx, client only get a pointer
> pointing to the address wh
On Wed, Nov 14, 2012 at 11:50:06AM +0800, Wenchao Xia wrote:
> In order to resolve OOM issue, I am trying wrap all APIs using
> sunrpc, need some suggestion before coding.
Is the client/server approach really necessary or can you write a
library that invokes qemu-nbd/qemu-img?
If there is a sta
Hello,Paolo and Stefanha
In order to resolve OOM issue, I am trying wrap all APIs using
sunrpc, need some suggestion before coding.
There are some different way to implement, not sure which would be
better:
1 keep client as thin as possible, client stores opaque pointer used
in server side,
10 matches
Mail list logo
