From owner-freebsd-xen@FreeBSD.ORG Sun Feb 20 01:38:53 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 573331065672 for ; Sun, 20 Feb 2011 01:38:53 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0B67E8FC0A for ; Sun, 20 Feb 2011 01:38:52 +0000 (UTC) Received: by qwj9 with SMTP id 9so4104632qwj.13 for ; Sat, 19 Feb 2011 17:38:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:from :date:x-google-sender-auth:message-id:subject:to:cc:content-type; bh=zXf+pGCPnZMRFY43kPLWz3oRaYSegIfIEAXfbPByLcE=; b=WqOl6Bn7f91hRhkltcU5Diy6Bu6qpTZAim0gOEBVtCkyzQZugu2av35QZnasFN070+ itDnqx0pqxvIkLzNtqeJeANGIHgTNddb/iUHJyWZLEbQ0J0J7eGjKxVcsm3PNvdm8y7K xdZdYM9ZaVz9MtulctxzN4HLZWYgJaaam7yds= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=dD7tE/C6apMcbnhH/2NtQIJx2O1AHOukfswAr0K3ARoLaahcLmHNCX8CQMrf68e/CE OMTO374wDGYUo8qjD7sxwqJKS8GDjdV3gIO5CoE7sIYOku7t/w7MTPL21wvfB9EpJ45X 3TVOiPD4oBEdRTC2qCzQOW82PPQoVrbLxyfpo= Received: by 10.229.181.78 with SMTP id bx14mr1707070qcb.296.1298165932178; Sat, 19 Feb 2011 17:38:52 -0800 (PST) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.229.188.140 with HTTP; Sat, 19 Feb 2011 17:38:12 -0800 (PST) In-Reply-To: References: <4D5E7CF7.8020209@barafranca.com> <4D5E92F3.6050709@barafranca.com> From: Ivan Voras Date: Sun, 20 Feb 2011 02:38:12 +0100 X-Google-Sender-Auth: QzDs8zeljgEXU9q-GgFmvZUj9Ok Message-ID: To: Hugo Silva Content-Type: text/plain; charset=UTF-8 Cc: freebsd-xen@freebsd.org Subject: Re: XenServer? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 01:38:53 -0000 On 19 February 2011 00:25, Ivan Voras wrote: > No such luck here; I've just tried an amd64 machine (8-STABLE from > today) in a new installation of XenServer 5.6 and while the GENERIC > kernel works stable enough, the XENHVM kernel produces all kinds of > timer-related problems, accompanied by messages like: > > Feb 18 23:20:03 xbsd kernel: calcru: runtime went backwards from > 28669021884109 usec to 22622950 usec for pid 11 (idle) I've tried comparing the performance of GENERIC and XENHVM kernels on this machine with unixbench and it points to GENERIC being faster in everything - though I don't know if this is an artifact of bad timer behaviour (except for one test, more on this later). Here are the results: ==> unixbench-generic.txt <== TEST BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 13828395.1 1185.0 Double-Precision Whetstone 55.0 4104.6 746.3 Execl Throughput 43.0 885.8 206.0 File Copy 1024 bufsize 2000 maxblocks 3960.0 142874.0 360.8 File Copy 256 bufsize 500 maxblocks 1655.0 65855.0 397.9 File Copy 4096 bufsize 8000 maxblocks 5800.0 146858.0 253.2 Pipe Throughput 12440.0 936158.7 752.5 Pipe-based Context Switching 4000.0 54004.1 135.0 Process Creation 126.0 1519.2 120.6 Shell Scripts (8 concurrent) 6.0 343.0 571.7 System Call Overhead 15000.0 578046.6 385.4 ==> unixbench-xenhvm.txt <== TEST BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 13718470.5 1175.5 Double-Precision Whetstone 55.0 912662.7 165938.7 Execl Throughput 43.0 750.2 174.5 File Copy 1024 bufsize 2000 maxblocks 3960.0 96273.0 243.1 File Copy 256 bufsize 500 maxblocks 1655.0 79155.0 478.3 File Copy 4096 bufsize 8000 maxblocks 5800.0 91023.0 156.9 Pipe Throughput 12440.0 872682.9 701.5 Pipe-based Context Switching 4000.0 50348.4 125.9 Process Creation 126.0 1511.7 120.0 Shell Scripts (8 concurrent) 6.0 225.9 376.5 System Call Overhead 15000.0 561000.3 374.0 Only in the whetstone test (and consistently only in this one across multiple runs) is the test timing very visibly screwed up, which is obvious if observing test execution: it takes orders of magnitude longer than it should (hours) and produces order of magnitude "better" results than it should. It skews the "final score" so its unusable. Whetstone is FPU-intensive, unique among these tests. Just for comparison, here are the results on bare hardware, same OS & base hardware (MBO, CPU, RAM), different drives & number of CPUs: TEST BASELINE RESULT INDEX Dhrystone 2 using register variables 116700.0 15419836.3 1321.3 Double-Precision Whetstone 55.0 3566.9 648.5 Execl Throughput 43.0 2512.4 584.3 Pipe Throughput 12440.0 1079209.1 867.5 Pipe-based Context Switching 4000.0 94001.1 235.0 Process Creation 126.0 4752.0 377.1 System Call Overhead 15000.0 676244.5 450.8 The result of whetstone indicates that even the GENERIC kernel might have similar timer problems. From owner-freebsd-xen@FreeBSD.ORG Sun Feb 20 03:00:45 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E5C8106564A for ; Sun, 20 Feb 2011 03:00:45 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 6CB3E8FC17 for ; Sun, 20 Feb 2011 03:00:44 +0000 (UTC) Received: from desktop.xor.net (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1K30eNP012469; Sun, 20 Feb 2011 14:00:42 +1100 Message-ID: <4D6083DC.4070008@joovke.com> Date: Sun, 20 Feb 2011 14:00:44 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110203 Thunderbird/3.1.7 MIME-Version: 1.0 To: Ivan Voras References: <4D5E7CF7.8020209@barafranca.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-xen@freebsd.org Subject: Re: XenServer? X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 03:00:45 -0000 I mentioned it and found TSO to be the cause. if someone else has seen this issue too, would you mind getting them to comment on PR 154428? Thanks! On 02/19/11 02:10, Ivan Voras wrote: > On 18 February 2011 15:06, Hugo Silva wrote: > >> Performance seems to be acceptable. There's a gotcha with PF, which someone >> else mentioned in this list recently. One has to disable tcp.tso to get >> decent throughput. >> >> Disabling it enabled a colleague who is currently in Africa to go from >> stalled..2KB/s sftp connections to 70KB/s. > I hope that 70 kB/s is due to him being in Africa and not Xen+FreeBSD > performance :) I'm thinking of using this on a moderately loaded web > server (cca 5 GB/day traffic). > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Mon Feb 21 03:03:02 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E05C01065672 for ; Mon, 21 Feb 2011 03:03:02 +0000 (UTC) (envelope-from joovke@joovke.com) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.freebsd.org (Postfix) with ESMTP id 688C48FC18 for ; Mon, 21 Feb 2011 03:03:02 +0000 (UTC) Received: from desktop.xor.net (c122-106-11-245.rivrw1.nsw.optusnet.com.au [122.106.11.245]) by mail02.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id p1L32x83001976 for ; Mon, 21 Feb 2011 14:03:00 +1100 Message-ID: <4D61D5E2.7090008@joovke.com> Date: Mon, 21 Feb 2011 14:02:58 +1100 From: Alex User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.13) Gecko/20110203 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: xennet_get_responses: too many frags X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 03:03:03 -0000 Hi, Just started seeing this: xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 8 > max 5 xennet_get_responses: too many frags 8 > max 5 xennet_get_responses: too many frags 8 > max 5 xennet_get_responses: too many frags 9 > max 5 xennet_get_responses: too many frags 10 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 7 > max 5 xennet_get_responses: too many frags 6 > max 5 and on it goes. any ideas? Version is 8.2-RELEASE/amd64 From owner-freebsd-xen@FreeBSD.ORG Mon Feb 21 11:07:15 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A28610656D0 for ; Mon, 21 Feb 2011 11:07:15 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E10508FC0C for ; Mon, 21 Feb 2011 11:07:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p1LB7Evp075899 for ; Mon, 21 Feb 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p1LB7Eq4075897 for freebsd-xen@FreeBSD.org; Mon, 21 Feb 2011 11:07:14 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Feb 2011 11:07:14 GMT Message-Id: <201102211107.p1LB7Eq4075897@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 11:07:15 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o i386/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i o kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 22 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Feb 21 19:26:35 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A42481065673 for ; Mon, 21 Feb 2011 19:26:35 +0000 (UTC) (envelope-from gibbs@FreeBSD.org) Received: from aslan.scsiguy.com (ns1.scsiguy.com [70.89.174.89]) by mx1.freebsd.org (Postfix) with ESMTP id 709CD8FC16 for ; Mon, 21 Feb 2011 19:26:35 +0000 (UTC) Received: from [192.168.182.88] (70-91-204-25-BusName-SFBA.hfc.comcastbusiness.net [70.91.204.25]) (authenticated bits=0) by aslan.scsiguy.com (8.14.4/8.14.4) with ESMTP id p1LJQWif066578 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 21 Feb 2011 12:26:33 -0700 (MST) (envelope-from gibbs@FreeBSD.org) Message-ID: <4D62BC6B.3010402@FreeBSD.org> Date: Mon, 21 Feb 2011 12:26:35 -0700 From: "Justin T. Gibbs" Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.14) Gecko/20110207 Thunderbird/3.1.8 MIME-Version: 1.0 To: Alex References: <4D61D5E2.7090008@joovke.com> In-Reply-To: <4D61D5E2.7090008@joovke.com> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (aslan.scsiguy.com [70.89.174.89]); Mon, 21 Feb 2011 12:26:34 -0700 (MST) Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-xen@FreeBSD.org Subject: Re: xennet_get_responses: too many frags X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gibbs@FreeBSD.org List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Feb 2011 19:26:35 -0000 On 2/20/2011 8:02 PM, Alex wrote: > Hi, > > Just started seeing this: > > xennet_get_responses: too many frags 7 > max 5 This was fixed in head by SVN revision 218056. It needs to be merged back to -stable. I will do so once I return from travel and can test my merge properly. If someone else decides to beat me to it, I won't complain. :-) -- Justin From owner-freebsd-xen@FreeBSD.ORG Tue Feb 22 01:22:13 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ED15106566C; Tue, 22 Feb 2011 01:22:13 +0000 (UTC) (envelope-from snabb@epipe.com) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6224A8FC15; Tue, 22 Feb 2011 01:22:13 +0000 (UTC) Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2]) by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p1M1MAG8017276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Feb 2011 01:22:10 GMT (envelope-from snabb@epipe.com) X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p1M1MAG8017276 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default; t=1298337730; x=1298942530; bh=kjxi1ioXC0VoAYV3aliCPFl7kEUba64hReSmsU3tIqs=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=Gvc/hpkqKBWKQ/iLZttO1PXLNk9J+5FNrZNLwaEVgonrWimALnqQWFmfrUW9ZZIqF kz3jsSO8qfGhDYQidRuJlDoC4yQYXDG6F5DZ+rZufbFOndmmrKpsgtJrXuKmZBiGuX DwgLbK0gBl7a0r2BvC0mLt5Cgr8pR6k/ekyEc1hk= Date: Tue, 22 Feb 2011 01:22:10 +0000 (UTC) From: Janne Snabb To: "Justin T. Gibbs" In-Reply-To: <4D62BC6B.3010402@FreeBSD.org> Message-ID: References: <4D61D5E2.7090008@joovke.com> <4D62BC6B.3010402@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6 (tiktik.epipe.com [IPv6:2001:1828:0:3::2]); Tue, 22 Feb 2011 01:22:10 +0000 (UTC) Cc: freebsd-xen@freebsd.org Subject: Re: xennet_get_responses: too many frags X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Feb 2011 01:22:13 -0000 On Mon, 21 Feb 2011, Justin T. Gibbs wrote: > On 2/20/2011 8:02 PM, Alex wrote: > > xennet_get_responses: too many frags 7 > max 5 > > This was fixed in head by SVN revision 218056. Ok, so the "if (frags > max)" check was unnecessary on FreeBSD, as speculated on this list previously. Thanks for figuring this out for us! The appropriate patch for folks who want to test or implement this is at: http://svn.freebsd.org/viewvc/base/head/sys/dev/xen/netfront/netfront.c?view=patch&r1=218056&r2=218055&pathrev=218056 It looks like the 8.2 release engineering process has moved past the RC stage, so I suppose it is too late to have this and some of the other Xen patches included in 8.2. -- Janne Snabb / EPIPE Communications snabb@epipe.com - http://epipe.com/