From mboxrd@z Thu Jan 1 00:00:00 1970 From: Henrik Holst Subject: Re: massive performance drop after a while when using virtio nics Date: Tue, 09 Sep 2008 13:11:10 +0200 Message-ID: <1220958670.12175.8.camel@henrik-desktop> References: <1219519317.2909.12.camel@decade.local> <1220955720.12615.28.camel@muff> <1220956332.3011.4.camel@decade.local> <1220957235.12615.47.camel@muff> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Fabian Deutsch , kvm@vger.kernel.org To: Mark McLoughlin Return-path: Received: from fg-out-1718.google.com ([72.14.220.158]:37228 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752691AbYIILLP (ORCPT ); Tue, 9 Sep 2008 07:11:15 -0400 Received: by fg-out-1718.google.com with SMTP id 19so1803576fgg.17 for ; Tue, 09 Sep 2008 04:11:13 -0700 (PDT) In-Reply-To: <1220957235.12615.47.camel@muff> Sender: kvm-owner@vger.kernel.org List-ID: 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? /Henrik Holst Witsbits AB