[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH] Fix the very-slow-IDE-IO-speed issue of Qemu 0.90

  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
  • Date: Mon, 28 May 2007 19:15:25 +0800
  • Delivery-date: Mon, 28 May 2007 04:13:51 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcehGX2iATPOwCb2S/eEWjt/qOrhsA==
  • Thread-topic: [PATCH] Fix the very-slow-IDE-IO-speed issue of Qemu 0.90

c/s 15021 updated Qemu to 0.90. In the new Qemu's ide.c, asynchronous IO
(AIO) is used to replace the previous DMA thread; here when an AIO
request is completed, dom0 sends a signal SIGUSR2 to Qemu (see
block-raw.c: qemu_aio_init(),raw_aio_setup()), then the signal
interrupts the select() in main_loop_wait() at once, next,
qemu_aio_poll() is called to reap a completed AIO request.

However, in certain Linux distributions (i.e., x86_64 RHEL 4u4), if Qemu
is spawned by the python script image.py of Control Panel, the SIGUSR2
of Qemu is blocked by default due to some reasons (i.e. it seems Python
2.3.4 has this issue; 2.4.2 is ok); so in most cases the select() in
main_loop_wait() can only time out in 10ms, then the qemu_aio_poll() is
called - this results in a very slow disk IO speed...

The attached patch ensures aio_sig_num is unblocked when the AIO is used
in Qemu 0.90.

Signed-off-by: Dexuan Cui <dexuan.cui@xxxxxxxxx>

Attachment: block-raw.c.patch
Description: block-raw.c.patch

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.