From: Gerd Hoffmann <kraxel@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel@nongnu.org, airlied@redhat.com
Subject: Re: [Qemu-devel] [PATCH 00/18] virgl: use a seperate rendering thread
Date: Thu, 08 Sep 2016 08:01:31 +0200 [thread overview]
Message-ID: <1473314491.6698.5.camel@redhat.com> (raw)
In-Reply-To: <20160904222039.11460-1-marcandre.lureau@redhat.com>
Hi,
> The benchmarks are quite encouraging, since I get from +-25% for
> xonotic up to +-100% for glmark. (fwiw, vhost-user-gpu had similar
> results too). Finally, I tried to make it acceptable for upstream.
Hmm, I don't feel like adding too many modes to virgl ...
With vhost-user-gpu giving us simliar benefits I'd prefer to focus on
that, for the additional security benefits (sandboxing the separate
process).
cheers,
Gerd
next prev parent reply other threads:[~2016-09-08 6:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 22:20 [Qemu-devel] [PATCH 00/18] virgl: use a seperate rendering thread Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 01/18] console: skip same-size resize Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 02/18] console: add dpy_gl_ctx_is_mt_safe Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 03/18] virtio-gpu: add "iothread" property Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 04/18] virtio-gpu: start splitting scanout/resource flushing Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 05/18] virtio-gpu: start introducing a lock around the display info Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 06/18] virtio-gpu: create a thread context Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 07/18] gl: allow to keep current context in ctx-create Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 08/18] gl: bind GL api before context creation Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 09/18] bitmap: add a simple foreach util Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 10/18] virtio-blk: use bitmap_foreach Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 11/18] virtio-gpu: use a bh for cursor modifications Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 12/18] virtio-gpu: save a pointer from virtio_gpu_ctrl_command Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 13/18] virtio-gpu: add a virgl data-plane Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 14/18] virtio-gpu: batch virtio_notify when using a data-plane Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 15/18] virtio-gpu: dispatch to main thread for scanout & flush Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 16/18] virtio-gpu: use virgl thread sync with the data-plane Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 17/18] virtio-gpu: schedule a bh to unblock " Marc-André Lureau
2016-09-04 22:20 ` [Qemu-devel] [PATCH 18/18] virtio-gpu: start/stop " Marc-André Lureau
2016-09-04 22:46 ` [Qemu-devel] [PATCH 00/18] virgl: use a seperate rendering thread no-reply
2016-09-04 22:48 ` no-reply
2016-09-08 6:01 ` Gerd Hoffmann [this message]
2016-09-08 6:38 ` Marc-André Lureau
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=1473314491.6698.5.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=marcandre.lureau@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.