From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BjHCf-0003IE-UQ for qemu-devel@nongnu.org; Sat, 10 Jul 2004 08:43:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BjHCf-0003I2-DP for qemu-devel@nongnu.org; Sat, 10 Jul 2004 08:43:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BjHCf-0003Hz-Av for qemu-devel@nongnu.org; Sat, 10 Jul 2004 08:43:41 -0400 Received: from [62.253.162.41] (helo=mta01-svc.ntlworld.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BjHAF-0007Kk-Hp for qemu-devel@nongnu.org; Sat, 10 Jul 2004 08:41:11 -0400 From: Julian Seward Subject: Re: [Qemu-devel] Reducing X communication bandwidth Date: Sat, 10 Jul 2004 13:42:34 +0100 References: <200407100945.06998.jseward@acm.org> <40EFDA42.2070704@wasp.net.au> In-Reply-To: <40EFDA42.2070704@wasp.net.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200407101342.34256.jseward@acm.org> Reply-To: jseward@acm.org, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Brad Campbell Cc: qemu-devel@nongnu.org > > Anyway, QEMU from cvs is unusable like this, at least when > > running WinXP or Win2K. The SDL layer (qemu/sdl.c) blasts > > huge numbers of pixels across the network in response to even > > the simplest graphical operations. Notably, moving the mouse > > pointer is appalling, with an update rate of about twice per > > second, which is hopeless. > > Great patch! This patch combined with ssh -X -C makes qemu usable over my > wireless link between office and home. Still a little laggy but at least > usable. Cool. You might want to experiment with the THRESH value in sdl.c to get the best performance. I set it to 32 and that works pretty well for me, but I'm not claiming it's optimal -- I only tried 16 and 32, and 32 was better. You can use any value >= 1. It controls the size of the blocks of pixels over which the patch makes send/no-send decisions. J