From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35815) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VIKVM-0002KR-RD for qemu-devel@nongnu.org; Sat, 07 Sep 2013 11:33:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VIKVE-0001nf-8X for qemu-devel@nongnu.org; Sat, 07 Sep 2013 11:32:56 -0400 MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_KLcoblrUlZGglr4pfMz9JA)" From: Yaodong Yang Date: Sat, 07 Sep 2013 15:32:48 +0000 (GMT) Message-id: Subject: [Qemu-devel] Block-migration and io thread contention List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, qemu-discuss@nongnu.org Cc: Yaodong Yang --Boundary_(ID_KLcoblrUlZGglr4pfMz9JA) Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: quoted-printable Hi all,=0A=0AInside qemu, there is block-migration feature, like migrate -= b. There is also a migrate_set_speed feature inside the monitor to control= the migration thread. I am wondering can we make some setting to let migr= ation thread yield to Io thread, or let the migration thread has the highe= r priority than io thread? In this way, we do not need to specify a max va= lue for migration thread. I think this way may be better.=0A=0AAny comment= s or suggestions are more than welcome!=A0=0A=0AYaodong= --Boundary_(ID_KLcoblrUlZGglr4pfMz9JA) Content-type: multipart/related; boundary="Boundary_(ID_pz7z0lw1B0Mpz6zqrSEE6A)"; type="text/html" --Boundary_(ID_pz7z0lw1B0Mpz6zqrSEE6A) Content-type: text/html; CHARSET=US-ASCII Content-transfer-encoding: 7BIT
Hi all,

Inside qemu, there is block-migration feature, like migrate -b. There is also a migrate_set_speed feature inside the monitor to control the migration thread. I am wondering can we make some setting to let migration thread yield to Io thread, or let the migration thread has the higher priority than io thread? In this way, we do not need to specify a max value for migration thread. I think this way may be better.

Any comments or suggestions are more than welcome! 

Yaodong
--Boundary_(ID_pz7z0lw1B0Mpz6zqrSEE6A)-- --Boundary_(ID_KLcoblrUlZGglr4pfMz9JA)--