[Spice-devel] [PATCH spice-protocol 2/2] Add qos related messages

Marc-André Lureau marcandre.lureau at gmail.com
Tue Apr 10 02:25:47 PDT 2012


Hi

On Tue, Apr 10, 2012 at 11:19 AM, Yonit Halperin <yhalperi at redhat.com> wrote:
> On 04/10/2012 12:13 PM, Marc-André Lureau wrote:
>>
>> On Sun, Apr 8, 2012 at 5:42 PM, Yonit Halperin<yhalperi at redhat.com>
>>  wrote:
>>>
>>> If the client's channel has SPICE_COMMON_CAP_QOS_QUERY,
>>> the server's channel can send SPICE_MSG_QOS_QUERY to the client.
>>> In response, the client is expected to send back SPICE_MSG_QOS_ACK
>>> immediately after it receives the message following the query, and
>>> before handling the message. The server can deduce
>>> the network condition using the ack arrival time.
>>
>>
>> Can it deduce other things than latency with this query?
>>
> You can deduce the bit rate, the ack is expected  only after receiving the
> message following the QOS_QUERY. So you can send the QOS_QUERY just before
> you are about to send a large message.
>

When you send QOS_QUERY, how do you know how much data is about to be
send? there could be data buffer locally, in process, in kernel, in
net hardware, in the network, in the client etc...

Wouldn't it be more reliable to put the QOS_QUERY in front of the data
to send, specifying the amount of data that is going to be send, so it
measures more precisely network bandwith?

-- 
Marc-André Lureau


More information about the Spice-devel mailing list