qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2


From: Avi Kivity
Subject: Re: [Qemu-devel] Anyone seeing huge slowdown launching qemu with Linux 2.6.35?
Date: Tue, 03 Aug 2010 19:44:49 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.7) Gecko/20100720 Fedora/3.1.1-1.fc13 Lightning/1.0b2pre Thunderbird/3.1.1

 On 08/03/2010 07:28 PM, Richard W.M. Jones wrote:
On Tue, Aug 03, 2010 at 07:10:18PM +0300, Avi Kivity wrote:
-kernel and -initrd is a developer's interface intended to make life
easier for users that use qemu to develop kernels.  It was not
intended as a high performance DMA engine.  Neither was the firmware
_configuration_ interface.  That is what virtio and to a lesser
extent IDE was written to perform.  You'll get much better results
from them.
Firmware configuration replaced something which was already working
really fast -- preloading the images into memory -- with something
which worked slower, and has just recently got _way_ more slow.

This is a regression.  Plain and simple.

It's only a regression if there was any intent at making this a performant interface. Otherwise any change an be interpreted as a regression. Even "binary doesn't hash to exact same signature" is a regression.

I have posted a small patch which makes this 650x faster without
appreciable complication.

It doesn't appear to support live migration, or hiding the feature for -M older.

It's not a good path to follow. Tomorrow we'll need to load 300MB initrds and we'll have to rework this yet again. Meanwhile the kernel and virtio support demand loading of any image size you'd want to use.

--
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]