From: Stefan Hajnoczi <stefanha@gmail.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC] libqblock OOM issue
Date: Wed, 14 Nov 2012 09:45:09 +0100 [thread overview]
Message-ID: <20121114084509.GB23826@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <50A314EE.6080801@linux.vnet.ibm.com>
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 startup cost problem with qemu-img it may be possible to
add an interactive mode (like qemu-io) where qemu-img stays open and
responds to commands (maybe in JSON encoding).
The difference between this and the RPC approach is that you can write a
relatively thin NBD and qemu-img library with the tools that already
exist today.
Stefan
next prev parent reply other threads:[~2012-11-14 8:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50A313A5.8030500@linux.vnet.ibm.com>
2012-11-14 3:50 ` [Qemu-devel] [RFC] libqblock OOM issue Wenchao Xia
2012-11-14 8:45 ` Stefan Hajnoczi [this message]
2012-11-14 9:55 ` Wenchao Xia
2012-11-14 10:32 ` Paolo Bonzini
2012-11-15 4:18 ` Wenchao Xia
2012-11-15 10:31 ` Paolo Bonzini
2012-11-15 12:21 ` Wenchao Xia
2012-11-15 12:34 ` Paolo Bonzini
2012-11-14 8:55 ` Paolo Bonzini
2012-11-14 10:06 ` Wenchao Xia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121114084509.GB23826@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiawenc@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).