All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: dlaor@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com,
	avi@redhat.com, danken@redhat.com
Subject: [Qemu-devel] Re: [PATCH 1/2] block: Add wr_highest_sector blockstat
Date: Thu, 29 Apr 2010 11:48:43 +0200	[thread overview]
Message-ID: <4BD955FB.8020308@redhat.com> (raw)
In-Reply-To: <4BD85BC8.50603@codemonkey.ws>

Am 28.04.2010 18:01, schrieb Anthony Liguori:
> On 04/28/2010 10:56 AM, Kevin Wolf wrote:
>> This adds the wr_highest_sector blockstat which implements what is generally
>> known as the high watermark. It is the highest offset of a sector written to
>> the respective BlockDriverState since it has been opened.
>>
>> The query-blockstat QMP command is extended to add this value to the result,
>> and also to add the statistics of the underlying protocol in a new "parent"
>> field. Note that to get the "high watermark" of a qcow2 image, you need to look
>> into the wr_highest_sector field of the parent (which can be a file, a
>> host_device, ...). The wr_highest_sector of the qcow2 BlockDriverState itself
>> is the highest offset on the _virtual_ disk that the guest has written to.
>>
>> Signed-off-by: Kevin Wolf<kwolf@redhat.com>
>>    
> 
> I see, you did print out stats for each layer.
> 
> I don't think we should take 2/2.  I don't mind QMP having more features 
> than the user monitor.

I agree, just posted it because it felt incomplete without it and I
wanted to give you the choice.

The only use case in the user monitor I saw for it would have been qemu
development anyway. I can keep the patch in a local branch for this (or
just rewrite it when/if I need it - it's small enough).

Kevin

  parent reply	other threads:[~2010-04-29 10:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 15:56 [Qemu-devel] [PATCH 0/2] block: wr_highest_sector blockstat Kevin Wolf
2010-04-28 15:56 ` [Qemu-devel] [PATCH 1/2] block: Add " Kevin Wolf
2010-04-28 15:59   ` [Qemu-devel] " Anthony Liguori
2010-04-28 16:01   ` Anthony Liguori
2010-04-28 17:04     ` Luiz Capitulino
2010-04-28 17:47       ` Anthony Liguori
2010-04-28 20:31         ` Luiz Capitulino
2010-04-29 16:03         ` Daniel P. Berrange
2010-04-29  9:48     ` Kevin Wolf [this message]
2010-04-28 17:31   ` Luiz Capitulino
2010-04-29 10:00     ` Kevin Wolf
2010-04-29 17:32       ` Luiz Capitulino
2010-04-28 15:56 ` [Qemu-devel] [PATCH 2/2] block: Extend info blockstats monitor command Kevin Wolf

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=4BD955FB.8020308@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=danken@redhat.com \
    --cc=dlaor@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.