All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark McLoughlin <markmc@redhat.com>
To: Henrik Holst <henrik@witsbits.com>
Cc: Fabian Deutsch <fabian.deutsch@gmx.de>, kvm@vger.kernel.org
Subject: Re: massive performance drop after a while when using virtio nics
Date: Tue, 09 Sep 2008 12:41:09 +0100	[thread overview]
Message-ID: <1220960469.12615.56.camel@muff> (raw)
In-Reply-To: <1220958670.12175.8.camel@henrik-desktop>

On Tue, 2008-09-09 at 13:11 +0200, Henrik Holst wrote:
> tis 2008-09-09 klockan 11:47 +0100 skrev Mark McLoughlin:
> > On Tue, 2008-09-09 at 12:32 +0200, Fabian Deutsch wrote:
> > > Am Dienstag, den 09.09.2008, 11:22 +0100 schrieb Mark McLoughlin:
> > > > Hi,
> > > > 
> > > > On Sat, 2008-08-23 at 21:21 +0200, Fabian Deutsch wrote:
> > > > > Hey.
> > > > > 
> > > > > When running a guest in the following setup, I observ a "massive"
> > > > > performance decrease after a couple of gigabytes of transfrerred data.
> > > > > 
> > > > > other guests keep running fine (no regressions) and nothing unusual is
> > > > > observed on the host.
> > > > 
> > > > If you do "killall -ALRM qemu-kvm" after the slowdown has occurred, does
> > > > it make things speed up again for a while?
> > > > 
> > > 
> > > It seems so! 
> > > Fantastic.
> > > 
> > > > If so, the issue is fixed by:
> > > > 
> > > >   http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ba661292a2bc6ddd305a212b0526e5dc22195fe7
> > > > 
> > > > It also got applied in 2.6.26.3 and 2.6.25.16.
> > > > 
> > > 
> > > So it was some signaling-bug on the .. client side?
> > 
> > No, it was a kernel race condition causing the qemu-kvm process to stop
> > receiving SIGALRM signals.
> 
> So is it the host kernel that should be patched?

Yes.

(Or build qemu-kvm to not use signalfd)

Cheers,
Mark.


  reply	other threads:[~2008-09-09 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 19:21 massive performance drop after a while when using virtio nics Fabian Deutsch
2008-09-08 12:07 ` Yann Dupont
2008-09-08 13:16   ` Fabian Deutsch
2008-09-08 13:33     ` Yann Dupont
2008-09-09 10:22 ` Mark McLoughlin
2008-09-09 10:32   ` Fabian Deutsch
2008-09-09 10:47     ` Mark McLoughlin
2008-09-09 11:11       ` Henrik Holst
2008-09-09 11:41         ` Mark McLoughlin [this message]
2008-09-09 11:54   ` Yann Dupont

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=1220960469.12615.56.camel@muff \
    --to=markmc@redhat.com \
    --cc=fabian.deutsch@gmx.de \
    --cc=henrik@witsbits.com \
    --cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.