From owner-freebsd-xen@FreeBSD.ORG  Thu Jun 26 20:34:16 2014
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1904BF3A
 for <freebsd-xen@FreeBSD.org>; Thu, 26 Jun 2014 20:34:16 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0091825F2
 for <freebsd-xen@FreeBSD.org>; Thu, 26 Jun 2014 20:34:16 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.8/8.14.8) with ESMTP id s5QKYFIN058577
 for <freebsd-xen@FreeBSD.org>; Thu, 26 Jun 2014 21:34:15 +0100 (BST)
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-xen@FreeBSD.org
Subject: [Bug 191173] [xen] Poor file write performance on xen blockfront
Date: Thu, 26 Jun 2014 20:34:16 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: feld@FreeBSD.org
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: royger@freebsd.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-191173-23905-7Vs6Fygi40@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191173-23905@https.bugs.freebsd.org/bugzilla/>
References: <bug-191173-23905@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
 <freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen/>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
 <mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Jun 2014 20:34:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191173

Mark Felder <feld@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |feld@FreeBSD.org
           Assignee|freebsd-xen@FreeBSD.org     |royger@freebsd.org

--- Comment #2 from Mark Felder <feld@FreeBSD.org> ---
Please detail in the bug report the hardware in question. I've also seen what I
believe could be similar behavior on FreeBSD 10 VMs, but only on one cluster
with older CPUs.

The more data points we have the more likely this can be narrowed down.

Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.