From 86152436eb06a76e495425c1aa862833576fbc71 Mon Sep 17 00:00:00 2001 From: Peter Lieven Date: Fri, 5 Sep 2014 22:07:41 +0200 Subject: [PATCH] ui/vnc: set TCP_NODELAY 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 Signed-off-by: Gerd Hoffmann --- ui/vnc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/ui/vnc.c b/ui/vnc.c index f8d9b7db95..0fe6eff1b8 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); } } -- 2.11.4.GIT