qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm@vger.kernel.org, mst@redhat.com, mtosatti@redhat.com,
	qemu-devel@nongnu.org, blauwirbel@gmail.com,
	Alex Williamson <alex.williamson@redhat.com>,
	avi@redhat.com
Subject: Re: [Qemu-devel] Slow PXE boot in qemu.git (fast in qemu-kvm.git)
Date: Mon, 11 Apr 2011 18:05:23 -0300	[thread overview]
Message-ID: <20110411180523.219530d7@doriath> (raw)
In-Reply-To: <4DA35EE4.6090303@web.de>

On Mon, 11 Apr 2011 22:04:52 +0200
Jan Kiszka <jan.kiszka@web.de> wrote:

> On 2011-04-11 21:15, Luiz Capitulino wrote:
> > On Mon, 11 Apr 2011 13:00:32 -0600
> > Alex Williamson <alex.williamson@redhat.com> wrote:
> > 
> >> On Mon, 2011-04-11 at 15:35 -0300, Luiz Capitulino wrote:
> >>> On Fri, 08 Apr 2011 19:50:57 -0500
> >>> Anthony Liguori <anthony@codemonkey.ws> wrote:
> >>>
> >>>> On 04/08/2011 06:25 PM, Luiz Capitulino wrote:
> >>>>> Hi there,
> >>>>>
> >>>>> Summary:
> >>>>>
> >>>>>   - PXE boot in qemu.git (HEAD f124a41) is quite slow, more than 5 minutes. Got
> >>>>>     the problem with e1000, virtio and rtl8139. However, pcnet *works* (it's
> >>>>>     as fast as qemu-kvm.git)
> >>>>>
> >>>>>   - PXE boot in qemu-kvm.git (HEAD df85c051) is fast, less than a minute. Tried
> >>>>>     with e1000, virtio and rtl8139 (I don't remember if I tried with pcnet)
> >>>>>
> >>
> >> I was having this problem too, but I think it's because I forgot to
> >> build qemu with --enable-io-thread, which is the default for qemu-kvm.
> >> Can you re-configure and build with that and see if it's fast?  Thanks,
> > 
> > Yes, nice catch, it's faster with I/O thread enabled, even seem faster
> > than qemu-kvm.git.
> 
> What's the performance under qemu-kvm with -no-kvm-irqchip?

Still fast, but just realized that qemu-kvm's configure says that I/O thread
is disabled:

 IO thread         no

And it's fast..

> 
> > 
> > So, does this have to be fixed w/o I/O thread?
> 
> If it's most probably an architectural deficit of non-io-thread mode, I
> would say let it rest in peace. But maybe it points to a generic issues
> that is just magnified by non-threaded mode.
> 
> Jan
> 

  parent reply	other threads:[~2011-04-12  1:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 23:25 [Qemu-devel] Slow PXE boot in qemu.git (fast in qemu-kvm.git) Luiz Capitulino
2011-04-09  0:50 ` [Qemu-devel] " Anthony Liguori
2011-04-09 12:03   ` Stefan Hajnoczi
2011-04-10  8:19   ` Avi Kivity
2011-04-11 18:35   ` [Qemu-devel] " Luiz Capitulino
2011-04-11 19:00     ` Alex Williamson
2011-04-11 19:15       ` Luiz Capitulino
2011-04-11 20:04         ` Jan Kiszka
2011-04-11 20:14           ` Alex Williamson
2011-04-11 20:18             ` Jan Kiszka
2011-04-11 20:29               ` Jan Kiszka
2011-04-12  8:09               ` Paolo Bonzini
2011-04-11 21:05           ` Luiz Capitulino [this message]
2011-04-11 21:18             ` Jan Kiszka
2011-04-12  0:39           ` Anthony Liguori
2011-04-12  7:42             ` Avi Kivity
2011-04-09 10:34 ` [Qemu-devel] " Blue Swirl
2011-04-11 12:51   ` Luiz Capitulino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110411180523.219530d7@doriath \
    --to=lcapitulino@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).