| commit | 86152436eb06a76e495425c1aa862833576fbc71 | |
| author | Peter Lieven <pl@kamp.de> | |
| Fri, 5 Sep 2014 20:07:41 +0000 (5 22:07 +0200) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Wed, 17 Sep 2014 13:14:41 +0000 (17 15:14 +0200) | ||
| tree | 8bed12785c8a67a91c12fd19f43a02ee090a4764 | treesnapshot (tar.gz zip) |
| parent | e4d50d47a9eb15f42bdd561803a29a4d7c3eb8ec | commitdiff |
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 <pl@kamp.de>
Signed-off-by: Gerd Hoffmann <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 <pl@kamp.de>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
| ui/vnc.c | diffblobblamehistory |