From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Saptarshi Sen <saptarshi.mrg@gmail.com>,
qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] ARRAYS :QMP Declaration
Date: Tue, 16 Jul 2013 09:02:16 -0500 [thread overview]
Message-ID: <20130716140216.21868.62612@loki> (raw)
In-Reply-To: <CAG5Np+qC3uC3m+C7aoFmG=iXwVYxf_kn-GrJa6rSm7nTadpmVw@mail.gmail.com>
Quoting Saptarshi Sen (2013-07-15 20:27:27)
> Hi,
>
> Is it possible to use fixed array data structures for use through the
> qmp-interface.
>
> My aim is to monitor IDE level activity in terms of sectors being
> accessed. So
> I plan to have a fixed size buffer. But I find no way of doing so when
> I use the
> qapi-schema.json.
> I think the qmp -interface uses linked lists as a replacement for array
> type structures.
>
> Can anybody clarify my doubt and whether is it possible to use arrays
> as in my case.
Not currently, though there is a plan to support it, likely in 1.7.
You can have your implementation map the buffer to a linked list type before
sending a response though. It's not particularly efficient... but then again
how big is this buffer gonna be? capacity/sector_size? If so I don't think
that's realistic over QMP. A list of active sector numbers might actually
work better. That could still be done more efficiently using arrays if we
supported them currently, but in practice I don't think the extra overhead
would be that much worse (though I'm assuming here that the number of sectors
being concurrently accessed would be relatively small)
>
> Regards
> Saptarshi Sen
prev parent reply other threads:[~2013-07-16 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 1:27 [Qemu-devel] ARRAYS :QMP Declaration Saptarshi Sen
2013-07-16 13:30 ` Luiz Capitulino
2013-07-16 14:02 ` Michael Roth [this message]
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=20130716140216.21868.62612@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=saptarshi.mrg@gmail.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.