From: Peter Lieven <pl@kamp.de>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 08/10] name vnc buffers
Date: Fri, 25 Sep 2015 09:28:55 +0200 [thread overview]
Message-ID: <5604F7B7.1090207@kamp.de> (raw)
In-Reply-To: <1443084128-25552-9-git-send-email-kraxel@redhat.com>
Am 24.09.2015 um 10:42 schrieb Gerd Hoffmann:
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> ui/vnc-jobs.c | 1 +
> ui/vnc.c | 16 ++++++++++++++++
> 2 files changed, 17 insertions(+)
>
> diff --git a/ui/vnc-jobs.c b/ui/vnc-jobs.c
> index 9824c34..7a234da 100644
> --- a/ui/vnc-jobs.c
> +++ b/ui/vnc-jobs.c
> @@ -303,6 +303,7 @@ static VncJobQueue *vnc_queue_init(void)
>
> qemu_cond_init(&queue->cond);
> qemu_mutex_init(&queue->mutex);
> + qio_buffer_init(&queue->buffer, "vnc-job-queue");
> QTAILQ_INIT(&queue->jobs);
> return queue;
> }
> diff --git a/ui/vnc.c b/ui/vnc.c
> index e4b0e3a..fc0311f 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -2978,6 +2978,22 @@ static void vnc_connect(VncDisplay *vd, int csock,
> vs->csock = csock;
> vs->vd = vd;
>
> + qio_buffer_init(&vs->input, "vnc-input/%d", csock);
> + qio_buffer_init(&vs->output, "vnc-output/%d", csock);
> + qio_buffer_init(&vs->ws_input, "vnc-ws_input/%d", csock);
> + qio_buffer_init(&vs->ws_output, "vnc-ws_output/%d", csock);
> + qio_buffer_init(&vs->jobs_buffer, "vnc-jobs_buffer/%d", csock);
> +
> + qio_buffer_init(&vs->tight.tight, "vnc-tight/%d", csock);
> + qio_buffer_init(&vs->tight.zlib, "vnc-tight-zlib/%d", csock);
> + qio_buffer_init(&vs->tight.gradient, "vnc-tight-gradient/%d", csock);
> + qio_buffer_init(&vs->tight.jpeg, "vnc-tight-jpeg/%d", csock);
> + qio_buffer_init(&vs->tight.png, "vnc-tight-png/%d", csock);
png and jpeg support is not generally available:
diff --git a/ui/vnc.c b/ui/vnc.c
index fc0311f..454087f 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -2987,8 +2987,12 @@ static void vnc_connect(VncDisplay *vd, int csock,
qio_buffer_init(&vs->tight.tight, "vnc-tight/%d", csock);
qio_buffer_init(&vs->tight.zlib, "vnc-tight-zlib/%d", csock);
qio_buffer_init(&vs->tight.gradient, "vnc-tight-gradient/%d", csock);
+#ifdef CONFIG_VNC_JPEG
qio_buffer_init(&vs->tight.jpeg, "vnc-tight-jpeg/%d", csock);
+#endif
+#ifdef CONFIG_VNC_PNG
qio_buffer_init(&vs->tight.png, "vnc-tight-png/%d", csock);
+#endif
qio_buffer_init(&vs->zlib.zlib, "vnc-zlib/%d", csock);
qio_buffer_init(&vs->zrle.zrle, "vnc-zrle/%d", csock);
qio_buffer_init(&vs->zrle.fb, "vnc-zrle-fb/%d", csock);
Peter
next prev parent reply other threads:[~2015-09-25 7:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 8:41 [Qemu-devel] [RfC PATCH 00/10] vnc buffer handling Gerd Hoffmann
2015-09-24 8:41 ` [Qemu-devel] [RfC PATCH 01/10] io/ makefile fluff Gerd Hoffmann
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 02/10] io: pull Buffer code out of VNC module Gerd Hoffmann
2015-09-25 9:57 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 03/10] vnc: make the Buffer capacity increase in powers of two Gerd Hoffmann
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 04/10] io: add qio_buffer_init Gerd Hoffmann
2015-09-25 9:56 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 05/10] io: add qio_buffer_move_empty Gerd Hoffmann
2015-09-25 9:56 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 06/10] io: add qio_buffer_move Gerd Hoffmann
2015-09-25 9:57 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 07/10] io: add qio_buffer tracing Gerd Hoffmann
2015-09-25 8:10 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 08/10] name vnc buffers Gerd Hoffmann
2015-09-25 7:28 ` Peter Lieven [this message]
2015-09-25 7:58 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 09/10] vnc: kill jobs queue buffer Gerd Hoffmann
2015-09-25 9:57 ` Peter Lieven
2015-09-24 8:42 ` [Qemu-devel] [RfC PATCH 10/10] vnc-jobs: move buffer reset, use new buffer move Gerd Hoffmann
2015-09-25 9:39 ` Peter Lieven
2015-09-24 16:25 ` [Qemu-devel] [RfC PATCH 00/10] vnc buffer handling Daniel P. Berrange
2015-09-25 9:56 ` Peter Lieven
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=5604F7B7.1090207@kamp.de \
--to=pl@kamp.de \
--cc=kraxel@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.