virgl: avoid large inline transfers
authorGurchetan Singh <gurchetansingh@chromium.org>
Mon, 26 Nov 2018 17:54:04 +0000 (09:54 -0800)
committerErik Faye-Lund <erik.faye-lund@collabora.com>
Fri, 30 Nov 2018 11:20:41 +0000 (12:20 +0100)
commitd18492c64f0abb4eb638d2b213b4b1ff3d775965
tree18fc142e2777c621b6efe34eceaf7f2b982161ad
parentc0773315af76cd735152c322cb7f710b4b053148
virgl: avoid large inline transfers

We flush everytime the command buffer (16 kB) is full, which is
quite costly.

This improves

dEQP-GLES3.performance.buffer.data_upload.function_call.buffer_data.new_buffer.usage_stream_draw

from 111.16 MB/s to 1930.36 MB/s.

In addition, I made the benchmark produce buffers from 0 --> VIRGL_MAX_CMDBUF_DWORDS * 4,
and tried ((VIRGL_MAX_CMDBUF_DWORDS * 4) / 2), ((VIRGL_MAX_CMDBUF_DWORDS * 4) / 4), etc.

I didn't notice any clear differences, so let's just go with the most obvious
heuristic.

Tested-By: Gert Wollny <gert.wollny@collabora.com>
Reviewed-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
src/gallium/drivers/virgl/virgl_resource.c