From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M6uFe-0007F2-1M for qemu-devel@nongnu.org; Wed, 20 May 2009 18:27:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M6uFZ-0007ET-ED for qemu-devel@nongnu.org; Wed, 20 May 2009 18:27:05 -0400 Received: from [199.232.76.173] (port=44448 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M6uFZ-0007EN-98 for qemu-devel@nongnu.org; Wed, 20 May 2009 18:27:01 -0400 Received: from mx2.redhat.com ([66.187.237.31]:43520) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M6uFY-0000JY-RM for qemu-devel@nongnu.org; Wed, 20 May 2009 18:27:01 -0400 From: Glauber Costa Date: Wed, 20 May 2009 18:26:56 -0400 Message-Id: <1242858418-10553-1-git-send-email-glommer@redhat.com> Subject: [Qemu-devel] [PATCH 0/2] make migrate_set_speed work while migration is running List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: aliguori@us.ibm.com With this series of patches, migration speed can be increased/decreased while a migration is active. The first patch introduces a new set_rate_limit function that provides us with the infrastructure, while the second uses it for the migration code.