From: Paolo Bonzini <pbonzini@redhat.com>
To: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [RFC] libqblock OOM issue
Date: Thu, 15 Nov 2012 11:31:42 +0100 [thread overview]
Message-ID: <50A4C48E.8080902@redhat.com> (raw)
In-Reply-To: <50A46D1D.5040503@linux.vnet.ibm.com>
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 protocol, client keeps
> the API unchanged but implement a bit different than server, which
> may archieve the same effect as invoking qemu-img inside without string
> parsing.
I think the result would really not be simple...
> Not sure if libqblock now is blocked by OOM issue as 1st version to
> be reviewed. If you think it must be resolved first, I would add this
> wrapper quickly.
No, I was lost with the build problems. Please repost the last version
you have.
Paolo
next prev parent reply other threads:[~2012-11-15 10:31 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
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 [this message]
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=50A4C48E.8080902@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).