From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>,
uril@redhat.com, qemu-devel@nongnu.org,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/3]: BLOCK_WATERMARK QMP event
Date: Thu, 11 Mar 2010 17:09:56 +0200 [thread overview]
Message-ID: <4B9907C4.9030404@redhat.com> (raw)
In-Reply-To: <4B990718.90409@codemonkey.ws>
On 03/11/2010 05:07 PM, Anthony Liguori wrote:
>> Still, if management is actually interested in the change, not just
>> to grow the volume (perhaps to handle out-of-space, or to check
>> against a global disk low condition), the helper/driver then needs to
>> communicate with the management system, which is awkward.
>
> The management system can poll information from the block driver.
> Polling is not always evil :-)
In this particular case, it can even poll lvm directly (and I think it
does), as it needs global information.
So a variant of the raw driver might work here. Is there any way to
pass options to nested format drivers?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-11 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 22:53 [Qemu-devel] [PATCH 0/3]: BLOCK_WATERMARK QMP event Luiz Capitulino
2010-03-09 22:53 ` [Qemu-devel] [PATCH 1/3] block-qcow2: keep highest allocated offset Luiz Capitulino
2010-03-09 22:53 ` [Qemu-devel] [PATCH 2/3] monitor: Introduce block_watermark command Luiz Capitulino
2010-03-09 22:53 ` [Qemu-devel] [PATCH 3/3] QMP: Introduce BLOCK_WATERMARK event Luiz Capitulino
2010-03-09 23:03 ` [Qemu-devel] [PATCH 0/3]: BLOCK_WATERMARK QMP event Anthony Liguori
2010-03-09 23:18 ` Luiz Capitulino
2010-03-09 23:08 ` Anthony Liguori
2010-03-09 23:22 ` Luiz Capitulino
2010-03-09 23:25 ` Luiz Capitulino
2010-03-09 23:55 ` Anthony Liguori
2010-03-10 21:02 ` Luiz Capitulino
2010-03-09 23:46 ` Anthony Liguori
2010-03-10 8:40 ` Kevin Wolf
2010-03-10 21:09 ` Luiz Capitulino
2010-03-10 21:20 ` Anthony Liguori
2010-03-11 8:34 ` Kevin Wolf
2010-03-11 14:19 ` Anthony Liguori
2010-03-11 14:58 ` Avi Kivity
2010-03-11 15:07 ` Anthony Liguori
2010-03-11 15:09 ` Avi Kivity [this message]
2010-03-11 16:16 ` Kevin Wolf
2010-03-10 8:33 ` [Qemu-devel] " Kevin Wolf
2010-03-10 9:28 ` Christoph Hellwig
2010-03-10 21:11 ` Luiz Capitulino
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=4B9907C4.9030404@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=uril@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.