Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-15 Thread Paolo Bonzini
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

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-15 Thread Wenchao Xia
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

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-15 Thread Paolo Bonzini
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 capabilities via XDR

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread Stefan Hajnoczi
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

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread Paolo Bonzini
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 where

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread Wenchao Xia
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

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread Wenchao Xia
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

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread 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-img? If there is a startup cost

Re: [Qemu-devel] [RFC] libqblock OOM issue

2012-11-14 Thread Wenchao Xia
于 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-devel] [RFC] libqblock OOM issue

2012-11-13 Thread Wenchao Xia
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,