From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:33916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPznn-0007bb-NM for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:08:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XPznh-0002ox-Rh for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:08:11 -0400 Received: from mx-v6.kamp.de ([2a02:248:0:51::16]:35705 helo=mx01.kamp.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPznh-0002nz-Gi for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:08:05 -0400 From: Peter Lieven Date: Fri, 5 Sep 2014 22:07:41 +0200 Message-Id: <1409947661-19614-1-git-send-email-pl@kamp.de> Subject: [Qemu-devel] [PATCHv2] ui/vnc: set TCP_NODELAY List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, Peter Lieven , kraxel@redhat.com we currently have the Nagle algorithm enabled for all outgoing VNC updates. This may delay sensitive updates as mouse movements or typing in the console. As we currently prepare all data in a buffer and then send as much as we can disabling the Nagle algorithm should not cause big trouble. Well established VNC servers like TightVNC set TCP_NODELAY as well. A regular framebuffer update request generates exactly one framebuffer update which should be pushed out as fast as possible. Signed-off-by: Peter Lieven --- v1->v2: use socket_set_nodelay (Peter) ui/vnc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/ui/vnc.c b/ui/vnc.c index f8d9b7d..0fe6eff 100644 --- a/ui/vnc.c +++ b/ui/vnc.c @@ -2914,6 +2914,7 @@ static void vnc_listen_read(void *opaque, bool websocket) } if (csock != -1) { + socket_set_nodelay(csock); vnc_connect(vs, csock, false, websocket); } } -- 1.7.9.5